-
-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add invalid key error to Studio #728
Comments
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. |
@Mrc0113 not related to studio, a new rule should be added to spectral, I've created an issue here: stoplightio/spectral#2503 |
Thank you @Amzani |
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 ❤️ |
Describe the bug
The error message for an invalid key is vague. It would be ideal if a key did not use required characters
[a-zA-Z0-9\.\-_]+$
it should immediately be an error stating invalid key.I am unsure if this is an issue in the studio itself or the parser.
How to Reproduce
Slack conversation: https://asyncapi.slack.com/archives/C34F2JV0U/p1688058753622989
Expected behavior
It would be ideal if a key did not use required characters
[a-zA-Z0-9\.\-_]+$
it should immediately be an error stating invalid key.The text was updated successfully, but these errors were encountered: