-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
feat: adapt HTTP bindings to v3 #204
Conversation
Co-authored-by: Sergio Moya <1083296+smoya@users.noreply.github.com>
Co-authored-by: Lukasz Gornicki <lpgornicki@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
you do not update schema here but in the other repo?
@derberg yes 👍 |
/rtm |
[schemaObject]: https://www.asyncapi.com/docs/specifications/latest/#schemaObject |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a thought. Would be cool to have a redirect on the website that would let us point to the latest minor version of a major. For instance, something like:
[schemaObject]: https://www.asyncapi.com/docs/specifications/latest/#schemaObject | |
[schemaObject]: https://www.asyncapi.com/docs/specifications/3/#schemaObject |
Which would redirect to https://www.asyncapi.com/docs/specifications/3.0.0/#schemaObject for now but would resolve to https://www.asyncapi.com/docs/specifications/3.4.0/#schemaObject in the future (when 3.4.0 is out).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this is not implemented yet, I would love to have this in place. For sure super useful when sharing links to the ref for a particular major version. Did you create an issue in website @fmvilas ?
Description
This PR adapts the HTTP bindings to v3. This first round of review is just for the general structure changes.
TODO right before final review:
TODO after merge:
Related issue(s)
Related to #182