Message object name in channelItemObject message.ref field cannot contain whitespaces

[DharinaHanumunthadu]

Describe the bug

AsyncAPI document fails to parse on AsyncAPI studio when the message.$ref field in the channelItemObject contains a reference to a message object in which its name contains spaces, as opposed to being camel-cased.

Note that the schema object names on the other hand work fine with spacing in them when referenced in a message object.

How to Reproduce

Steps to reproduce the issue. Attach all resources that can help us understand the issue:

Test File with bug: testFile.csv

1. Copy paste the attached file contents into AsyncApi Studio
2. There are 2 diagnostic errors that show up (Referencing in this place is not allowed), on line 44 and 54

Screenshot:

Slack thread: https://asyncapi.slack.com/archives/C0230UAM6R3/p1681763680898089

Expected behavior

Expect the message object with name turn OnOff to be referenced without validation issues in message.$ref: '#/components/messages/turn OnOff' on lines 44 and 54

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup 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.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[darrylmacrae]

Is there a plan to address this issue in AsyncAPI v2 or v3 ?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️