Fix XMLTest.testIndentComplicatedJsonObjectWithArrayAndWithConfig() for Windows - in the test by Madjosz · Pull Request #778 · stleary/JSON-java · GitHub
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#593 and 85495fa included some workaround for Windows machines regarding linefeeds. The test org.json.junit.XMLTest.testIndentComplicatedJsonObjectWithArrayAndWithConfig() is currently failing on my Windows 10 machine and also I see no reason why this workaround was needed in the first place. The file Issue593.xml contains only \n line feeds and no conversion is done while reading this file, thus expected only contains \n. Conversely the tested method XML.toString() only appends hardcoded \n.
The only setting where the conversion is needed is when someone has their .gitattributes/Git settings or IDE configured to autoreplace linefeeds by the system default. In that case I would say it is actually correct that the test fails because it indicates a wrong setup.
@Madjosz Thanks for catching this! I had gotten out of the habit of testing on Windows.
stleary
changed the title
fix failing test XML test on Windows machines
Fix XMLTest.testIndentComplicatedJsonObjectWithArrayAndWithConfig() for Windows - in the code
Oct 6, 2023
stleary
changed the title
Fix XMLTest.testIndentComplicatedJsonObjectWithArrayAndWithConfig() for Windows - in the code
Fix XMLTest.testIndentComplicatedJsonObjectWithArrayAndWithConfig() for Windows - in the test
Oct 6, 2023
@Madjosz I prefer this version of the fix, but I cannot test it locally, probably because of recent commits. You will need to fix this if you want your PR to be considered.
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
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.
#593 and 85495fa included some workaround for Windows machines regarding linefeeds. The test
org.json.junit.XMLTest.testIndentComplicatedJsonObjectWithArrayAndWithConfig()is currently failing on my Windows 10 machine and also I see no reason why this workaround was needed in the first place. The fileIssue593.xmlcontains only\nline feeds and no conversion is done while reading this file, thusexpectedonly contains\n. Conversely the tested methodXML.toString()only appends hardcoded\n.The only setting where the conversion is needed is when someone has their
.gitattributes/Git settings or IDE configured to autoreplace linefeeds by the system default. In that case I would say it is actually correct that the test fails because it indicates a wrong setup.