Skip to content
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

Merged
merged 8 commits into from
Jul 25, 2023

Conversation

jonaslagoni
Copy link
Member

@jonaslagoni jonaslagoni commented Jun 13, 2023

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:

  • Adapt examples, if any that contain v2 structure.
  • Figure out which version change this constitutes

TODO after merge:

  • Adapt schema files in spec-schema-repo

Related issue(s)
Related to #182

@jonaslagoni jonaslagoni changed the base branch from master to next-major-spec June 22, 2023 10:23
@jonaslagoni jonaslagoni changed the title feat!: adapt HTTP bindings to v3 feat: adapt HTTP bindings to v3 Jun 22, 2023
http/README.md Outdated Show resolved Hide resolved
http/README.md Outdated Show resolved Hide resolved
@jonaslagoni
Copy link
Member Author

@fmvilas @smoya @derberg reverted the parameter object to schema 🙂

http/README.md Outdated Show resolved Hide resolved
Co-authored-by: Lukasz Gornicki <[email protected]>
http/README.md Show resolved Hide resolved
Copy link
Member

@derberg derberg left a 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?

@jonaslagoni
Copy link
Member Author

@derberg yes 👍

@jonaslagoni
Copy link
Member Author

/rtm

@asyncapi-bot asyncapi-bot merged commit 4841cf5 into asyncapi:next-major-spec Jul 25, 2023
6 checks passed
@jonaslagoni jonaslagoni deleted the v3_http branch July 25, 2023 13:07
[schemaObject]: https://www.asyncapi.com/docs/specifications/latest/#schemaObject
Copy link
Member

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:

Suggested change
[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).

Copy link
Member

@smoya smoya Aug 23, 2023

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 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants