-
-
Notifications
You must be signed in to change notification settings - Fork 309
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
XMLBuilder: Attributes with undefined
values produce odd whitespace when used with format: true
#585
Comments
We're glad you find this project helpful. We'll try to address this issue ASAP. You can vist https://solothought.com to know recent features. Don't forget to star this repo. |
Hi @amitguptagwl, I found the same odd behaviour. Moreover, there is another "odd" case with formatting enabled when attributes are specified as null. Using the same structure as the one of @FiniteLooper, with the starting object as follows const xmlObj = {
"list": {
"item":[
"one",
{"#text": "two"},
{"#text": "three", "@_attr": null},
{"#text": "two", "@_attr": "foo"}
]
}
}; the final output is <list>
<item>one</item>
<item>
three <@_attr/>
</item>
<item attr="foo">two</item>
</list> If this and the former are unexpected behaviours, I could fix them! I already looked at the code and it shouldn't be that hard. In that case, I think that the expected output should also be discussed (empty string in the attribute value, no attribute at all, etc.) |
Hi @cecia234, since |
…e skipped in the built xml
…e skipped in the built xml
NaturalIntelligence#585) Null and Undefined attributes should be suppressed when ignoreAttributes is false both when format is true and when it is false
Description
Using
XMLBuilder
when theformat: true
option is on and an array contains a property withundefined
as the value it produces odd whitespace formatting. The text is not on the same line as the opening XML tag, and there are several spaces added before the closing tag.The XML output is correct in how it creates the tags and their attributes, but the whitespace is just all wrong.
Code
Actual Output
Expected Output
What I am working on has optional object properties, so I just pass the data to the property as is. Here is my real use case in my TypeScript project
Would you like to work on this issue?
The text was updated successfully, but these errors were encountered: