Finally moving to official org.json implementation! - #194
Merged
carterpage merged 6 commits intoJul 19, 2024
Merged
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
added 6 commits
July 19, 2024 08:47
This requires replaceing "null" with JSONObject.NULL in arrays. Duplicate keys are now a syntax error, so two tests were updated.
…ow a RuntimeException.
…RuntimeException.
This was referenced Jul 26, 2024
Closed
Closed
Copy link
Copy Markdown
|
Hello @carterpage is there any plan to release this in a 2.0 release? Thanks a lot! |
Sorry, something went wrong.
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
2 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.
Fix for issue #179.
This is a fundamental change and will require a major version increment (2.0.0) at the next release.
Replace org.json dependency to use the org.json package.
Some behavioral changes / possible gotchas: