Fix spec mistakes found in final readthrough #644
Merged
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
- Update example to be compliant with OpenAPI v3.1 - Fix a broken example - Update Bean Validation requirements for OpenAPI v3.1 - Add schema model methods for custom properties to release notes - Update source code links to point to the main branch
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.
Doing a final readthrough of the spec, I noticed a few issues. Mostly minor apart from the Bean Validation requirements which hadn't been updated for OpenAPI 3.1 (though the TCK had been).
@sincetags to API classesForgetting to update the examples is easy to do so I've raised #645 for a future release to make sure we have a TCK for each example and the code is kept in sync.