JSONObject render fields in sorted order with -Dorg.json.fields.sort=true #80
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
added 2 commits
April 1, 2013 22:06
…s operate on their own JSONObjects instances concurrently
|
No thank you. JSON ordering is not significant. Making it significant will lead to bugs and interoperability failures. toString is a lousy way to test. |
BGehrels
pushed a commit
to BGehrels/JSON-java
that referenced
this pull request
Apr 29, 2020
New test to verify unclosed array
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.
The new Java versions(*) randomize the plain HashMap order making the current JSONObject.toString unusable in unit tests or other situations where the output could needs to be in same order on each run.
*) Java8 or Java7 with CVE fix enabling system property (http://docs.oracle.com/javase/7/docs/technotes/guides/collections/changes7.html)