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: add OpenAPI 3.0 schema validation #348

Conversation

jonaslagoni
Copy link
Member

Description
This PR adds OpenAPI 3.0 schema validation for message payloads that uses the schema formats:

"application/vnd.oai.openapi;version=3.0.0", 
"application/vnd.oai.openapi+json;version=3.0.0", 
"application/vnd.oai.openapi+yaml;version=3.0.0"

Based on the recommended schema formats: https://www.asyncapi.com/docs/reference/specification/v2.6.0#messageObjectSchemaFormatTable

Related issue(s)
Blocked by #334

@jonaslagoni jonaslagoni changed the base branch from master to next-major-spec February 22, 2023 22:15
@jonaslagoni
Copy link
Member Author

This PR is ready to be reviewed as #334 has been merged.

@jonaslagoni
Copy link
Member Author

Thanks @dalelane!

@sonarcloud
Copy link

sonarcloud bot commented Mar 14, 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

@jonaslagoni
Copy link
Member Author

/rtm

@asyncapi-bot asyncapi-bot merged commit 48e7b43 into asyncapi:next-major-spec Mar 14, 2023
@asyncapi-bot
Copy link
Contributor

🎉 This PR is included in version 5.0.0-next-major-spec.15 🎉

The release is available on:

Your semantic-release bot 📦🚀

@asyncapi-bot
Copy link
Contributor

🎉 This PR is included in version 6.0.0-next-major-spec.1 🎉

The release is available on:

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