-
-
Notifications
You must be signed in to change notification settings - Fork 54
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
validate extension with json schema #408
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. |
do we really need a new issue, the one #280 is clear, specifies what will be changed, there were no objections. So I do not see a need for new issue, we just need a PR 😄 |
ok then I am closing this one |
This issue is a part of
AsyncAPImentorship program
#78Main Objective
As part of the Mentorship program we need to validate the extensions with json schema.
A folder named
extensions
would be added just as bindings are present.Description
#280
In brief, An extension enables the description of functionality or protocol related features. Everyone can create their own extensions to give users more freedom on the spec.
We need to have a JSON Schema validation. In fact, to enable validation in the parser, we need JSON Schema for AsyncAPI to contain JSON Schemas of individual extensions.
The final objective is to have a catalog of extensions that users can browse and use. Then, as time goes by, we enhance the catalog according to the demands / needs.
cc: @derberg
The text was updated successfully, but these errors were encountered: