JSONObject map type unit tests #685
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
|
Starting a 3 day comment window |
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.
What problem does this code solve?
Set up unit tests for user-managed JSONObject map type. Ensure that all methods result in a JSONObject map type that matches the one created in the default constructor.
Risks
Low
Changes to the API?
Added a getMapType() method to JSONObject
Will this require a new release?
No
Should the documentation be updated?
No
Does it break the unit tests?
No
Was any code refactored in this commit?
A few unit tests were adjusted to make it easier to test multiple JSONObject and JSONArray instances.
Review status
APPROVED - by myself