You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, the specs we create will be missing sertain properties, as these will applied when the specification is submitted upstream, for instance seers. So it would be nice if we either can disable checks or suppress warnings, as this is poluting our CI/CD with irrelevant warnings.
How will this change help?
Will make the validate command output are more true result of warnings/errors
Screenshots
No response
How could it be implemented/designed?
Perhaps as an option in the schema such as: x-suppress-warnings
Where it list the warnings/tests that should be ignores
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.
Why do we need this improvement?
Sometimes, the specs we create will be missing sertain properties, as these will applied when the specification is submitted upstream, for instance seers. So it would be nice if we either can disable checks or suppress warnings, as this is poluting our CI/CD with irrelevant warnings.
How will this change help?
Will make the validate command output are more true result of warnings/errors
Screenshots
No response
How could it be implemented/designed?
Perhaps as an option in the schema such as:
x-suppress-warnings
Where it list the warnings/tests that should be ignores
🚧 Breaking changes
No
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue?
None
The text was updated successfully, but these errors were encountered: