feat!: full v3 support #8
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
About the PR
Upgraded models to reflect v3 asyncapi.
Full support for up- and downgrading specifications to and from 2.6.
When serializing v2.6 some things will be inferred and might not match expectation, but it is valid asyncapi.
fixed issues with reference resolution and ensured full resolution of fragments along with de-referencing targets.
BREAKING CHANGE: All models have changed to reflect v3.0
https://www.asyncapi.com/docs/reference/specification/v3.0.0
The API has been kept consistent with the specification, just like 2.6 was, so it will match 1:1 the official documentation.
Schemas are ALWAYS in the form of multiformatschema, this to ease development efforts.