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

docs: remove info about compatibility with openapi #933

Merged
merged 1 commit into from
May 23, 2023

Conversation

derberg
Copy link
Member

@derberg derberg commented May 11, 2023

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

@sonarcloud
Copy link

sonarcloud bot commented May 11, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@derberg
Copy link
Member Author

derberg commented May 23, 2023

/rtm

@asyncapi-bot asyncapi-bot merged commit 242c0f6 into asyncapi:next-major-spec May 23, 2023
@asyncapi-bot
Copy link
Contributor

🎉 This PR is included in version 3.0.0-next-major-spec.11 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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.

4 participants