Fix sorting of #/components/schemas/* - #50
Merged
langecode merged 1 commit intoJul 3, 2020
Conversation
Member
|
Doh. Thanks. I think I have time to quickly create a new release now. |
langecode
approved these changes
Jul 3, 2020
|
@hiddewie Thanks for the PR's made for this! Just wondering if there are plans to handle schemas that are not embedded in components (schemas defined in |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
There was a regression in e629216 (#49) that caused the result of
sortSchemasnot to be used.This regression made schemas non sorted.
A test has been added and the fix has been done.