-
-
Notifications
You must be signed in to change notification settings - Fork 262
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
Broken links - references to parts of OAS specification? #3
Comments
Awesome, didn't know about mdv. A PR would be much appreciated. |
And yes, it seems it's referencing some OAS part, but if I'm not wrong they are also applicable to AsyncAPI. |
|
IMO everything should be in the AsyncAPI document and not referencing OAS externally beacause the two specifications can evolve in a different way/pace. So I would just copy the missing pieces and paste them here. And in case it's different (like components object) we should redact its definition. What do you think? |
Add data type formats section, refs #3
Add componentsObject section, refs #3
@MikeRalphson it's working perfectly: https://travis-ci.org/asyncapi/asyncapi Thanks man 👏 |
Found by mdv, which runs as part of the OAS CI task.
Happy to raise a PR to add a CI step. I think all of the above need sections adding to the spec or links created to a version of the OAS spec?
The text was updated successfully, but these errors were encountered: