docs: remove info about compatibility with openapi #933
Conversation
This file contains 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
derberg
requested review from
fmvilas,
dalelane,
smoya,
char0n and
asyncapi-bot-eve
as code owners
|
Kudos, SonarCloud Quality Gate passed!
|
fmvilas
approved these changes
May 11, 2023
dalelane
approved these changes
May 14, 2023
|
/rtm |
asyncapi-bot
merged commit 242c0f6
into
asyncapi:next-major-spec
28 of 29 checks passed
|
🎉 This PR is included in version 3.0.0-next-major-spec.11 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Closed
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.
With 3.0 spec we are no longer really aiming for compatibility with OpenAPI, other than we do with other specs on schema level.
In other words, on schema level we still support OpenAPI Schema, Avro and many others.
So basically in case of OpenAPI there is no special treatment.
This is why this PR removes old 2.0 sentence about compatibility and instead we just leave the attribution for the great work of OpenAPI folks that inspired AsyncAPI
some more context: https://youtu.be/7urTb207V-8?t=121