fix: alphabetizeProperties option #2700
Open
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
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.
Description
alphabetizeProperties option does not work, this PR aims to fix this.
Another fix is default indent size is 4 for most of the json files.
Related Issue
#2698
Motivation and Context
Previous Behaviour / Output
No matter
alphabetizePropertiesis true or false, the output interface still sort the property in alphabet order.New Behaviour / Output
When not set or set to false, the default output properties are ordered in schema definition order. When set to true, the output order is in alphabet order.
How Has This Been Tested?
Testing code (default false):
Output (schema order):
Testing code (set to true):
Output (alphabet order):
Screenshots (if appropriate):