We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Version 1.1.10.37
For fun, I unflattened the convoluted document from my comment in #26:
{ "": { "": [ { "": "", "txDefinition": { "repeatRate": 0, "canPort": 0, "messageId": 0 } } ] } }
When I re-flatten this again, I get:
[ [ [ [ "", { "repeatRate":0, "canPort":0, "messageId":0 } ] ] ] ]
Objects have been transformed into arrays.
Also, notice the weird indentation of the innermost and 2nd-innermost arrays at the output.
The output is correct if I replace the empty names ("") with non-empty ones.
""
See https://stackoverflow.com/questions/33254385/can-a-json-name-value-pair-have-an-empty-name -- Empty strings are valid names for object members.
The text was updated successfully, but these errors were encountered:
@JKSH For what it's worth, I think we've resolved the "weird indentation" issue #31
Sorry, something went wrong.
No branches or pull requests
Version 1.1.10.37
For fun, I unflattened the convoluted document from my comment in #26:
When I re-flatten this again, I get:
Objects have been transformed into arrays.
Also, notice the weird indentation of the innermost and 2nd-innermost arrays at the output.
The output is correct if I replace the empty names (
""
) with non-empty ones.See https://stackoverflow.com/questions/33254385/can-a-json-name-value-pair-have-an-empty-name -- Empty strings are valid names for object members.
The text was updated successfully, but these errors were encountered: