-
Notifications
You must be signed in to change notification settings - Fork 92
Fix #231: Minimize empty elements with lengthy attributes #233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -749,4 +749,20 @@ class XMLTestJVM { | |
assertEquals("<node>\n <leaf/>\n</node>", pp.format(x)) | ||
} | ||
|
||
@UnitTest | ||
def issue231: Unit = { | ||
val pp = new xml.PrettyPrinter(4, 2, minimizeEmpty = true) | ||
val x = <a b="c"/> | ||
val formatted = pp.format(x) | ||
assertEquals(x, XML.loadString(formatted)) | ||
assertTrue(formatted.trim.lines.length >= 2) | ||
} | ||
|
||
@UnitTest | ||
def issue231_withoutAttributes: Unit = { | ||
val pp = new xml.PrettyPrinter(4, 2, minimizeEmpty = true) | ||
val x = <abcdefg/> | ||
val formatted = pp.format(x) | ||
assertEquals(x, XML.loadString(formatted)) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same here. The test should be of the string output from |
||
} | ||
} |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this test be comparing strings? With
XML.loadString
, I think you're just verifying the XML structure is preserved from the original.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm verifying that there are no extra nodes caused by the formatting, such as the
Text
node reported in #231.I didn't want to hard-code a string to avoid having to modify the test if the formatting behaviour changes. For example, if the commented-out
todo
is fixed, the output may have 3 lines instead of 2.Since the bug is about the XML structure changing (and, in my case, failing schema validation), I think that using
XML.loadString
is a better option.What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, ok. That's a fair point. The XML structure was getting changed.
There are other tests of
PrettyPrinter
that compare strings. If history is any guide, I don't think it's a huge risk for the formatting behavior to change often. Again, strings are the output ofPrettyPrint.format
, so it seems worth checking.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what value a string comparison would add. I think that the functionality of formatting is covered by other tests, e.g.
issue90
on line 746. This test also checks that some formatting happened by checking the number of lines in the output.I'll add the string comparison if you deem it necessary, but I don't think it would add much value.