fix: change schema name word breaking to anywhere

[Laupetin]

Description

Changes proposed in this pull request:

• Change schema name style word breaking to use overflow-wrap: anywhere to prevent content going under the sidebar when using long schema names that cannot be broken up into words.

Why is this an issue?
When using long names for schemas that cannot be broken up into words like when using Java package names, the content can go under the sidebar.
This makes the content unreadable to a large extent unless the window is made small enough for the sidebar to be put inside the burger menu.

When applying overflow-wrap: anywhere the browser will still try to wrap on words but also allows breaking up long, otherwise unbreakable strings to avoid overflowing.

Example

Previously:

Afterwards:

AsyncApi definition used for the example:

{
  "asyncapi": "2.4.0",
  "info": {
    "title": "Example API",
    "version": "0.1.0",
    "description": "An API for demonstration purposes"
  },
  "channels": {
    "exchange/my.routingkey": {
      "bindings": {
        "amqp": {
          "is": "routingKey",
          "queue": {
            "name": "my.routingkey"
          },
          "exchange": {
            "name": "exchange",
            "type": "topic"
          }
        }
      },
      "subscribe": {
        "description": "Informs about an example to be considered",
        "message": {
          "$ref": "#/components/messages/com.example.myapp.infrastructure._shared.messaging.dto.ExampleMessage"
        }
      }
    }
  },
  "components": {
    "messages": {
      "com.example.myapp.infrastructure._shared.messaging.dto.ExampleMessage": {
        "name": "Example message",
        "payload": {
          "type": "object",
          "properties": {
            "metadata": {
              "$ref": "#/components/schemas/com.example.myapp.infrastructure._shared.messaging.dto.SomeDtoClassThatIsUsedInsideAMessage"
            }
          }
        }
      }
    },
    "schemas": {
      "com.example.myapp.infrastructure._shared.messaging.dto.SomeDtoClassThatIsUsedInsideAMessage": {
        "name": "Example schema",
        "type": "object",
        "properties": {
          "testProperty": {
            "type": "string"
          }
        }
      }
    }
  }
}

Related issue(s)

[github-actions]

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[derberg]

Thanks!

[derberg]

/rtm

[jonaslagoni]

@derberg any update here?

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[derberg]

/rtm

[derberg]

next is probably way behind with latest CI/CD workflows
merging manually

[asyncapi-bot]

🎉 This PR is included in version 1.0.0-next.50 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀