Keep undefined nodes out of the XML output.#63
Merged
amitguptagwl merged 1 commit intoNaturalIntelligence:masterfrom Mar 5, 2018
Merged
Keep undefined nodes out of the XML output.#63amitguptagwl merged 1 commit intoNaturalIntelligence:masterfrom
amitguptagwl merged 1 commit intoNaturalIntelligence:masterfrom
Conversation
This is useful when you are deleting nodes from the JSON and rewriting XML. While I could see a case for writing an empty node in this case (`<b/>`), I'm fairly certain we never want the current behavior which is `<b>undefined</b>`.
Contributor
Author
|
(Sorry my editor also got rid of trailing whitespace on some lines) |
Member
|
Sorry for the late response, it's a festive season here. I will check and merge it on Monday. |
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
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.
This is useful when you are deleting nodes from the JSON and rewriting XML. While I could see a case for writing an empty node in this case (
<b/>), I'm fairly certain we never want the current behavior which is<b>undefined</b>.so if you have:
You get:
IMO you wanted: