Add editor-next.swagger.io as alternative validator for OpenAPI 3.1+ #741
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
![mintlify[bot]](https://avatars.githubusercontent.com/in/222410?s=60&v=4){kind=small}
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
This PR adds information about the newer Swagger editor (https://editor-next.swagger.io/) as an alternative validator for OpenAPI 3.1 and newer specifications. This tool is specifically useful for validating modern OAS formats that older validators might not fully support.
Updates were made in:
Both updates were made in sections addressing blank OpenAPI pages.