Initial implementation of XMLParserConfig object for flexible XML Parsing #412
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?
Implements improvement requested in #394 (see also #108, #286, #344). Adds a new configuration class that can be used to change how the XML Parser works.
Risks
Low. Current functionality works as expected.
Changes to the API?
3 new public APIs are available that take advantage of possible
public static JSONObject toJSONObject(Reader reader, XMLParserConfiguration config) throws JSONException
public static JSONObject toJSONObject(String string, XMLParserConfiguration config) throws JSONException
public static String toString(final Object object, final String tagName, final XMLParserConfiguration config)
A private method signature was also changed, but should not affect the API.
Will this require a new release?
Yes
Should the documentation be updated?
Yes
Does it break the unit tests?
No. No new unit tests were created yet, but we probably should add some.
Was any code refactored in this commit?
Not beyond extending the public APIs to use the new configuration object.
Review status
APPROVED