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
But I cannot reproduce that JSON output with version 0.2.1 (the latest), not with any of the -d options ('abdera', 'badgerfish', 'cobra', 'gdata', 'parker', 'xmldata', 'yahoo'). The option that yields the most similar output seems to be badgerfish, that produces the following list tagged "person" and containing objects that have the person data, which is a very different structure than what's shown in the README:
I didn't submit a PR correcting this because I don't know the real intent. I think the actual output is pretty confusing. Naively I expected minimal changes, with a list of "person" objects. That is arguably poor JSON (repeating the name every time) but it faithfully preserves the ugly XML input.
When the very first example is wrong, that makes the library fairly difficult to use or trust. Please reply, thanks.
The text was updated successfully, but these errors were encountered:
chrisinmtown
changed the title
First example in README does not match xmljson behavior version 0.2.0
First example in README does not match xmljson behavior version 0.2.1
Sep 1, 2020
The README offers the following sample XML input:
and JSON output:
But I cannot reproduce that JSON output with version 0.2.1 (the latest), not with any of the -d options ('abdera', 'badgerfish', 'cobra', 'gdata', 'parker', 'xmldata', 'yahoo'). The option that yields the most similar output seems to be badgerfish, that produces the following list tagged "person" and containing objects that have the person data, which is a very different structure than what's shown in the README:
I didn't submit a PR correcting this because I don't know the real intent. I think the actual output is pretty confusing. Naively I expected minimal changes, with a list of "person" objects. That is arguably poor JSON (repeating the name every time) but it faithfully preserves the ugly XML input.
When the very first example is wrong, that makes the library fairly difficult to use or trust. Please reply, thanks.
The text was updated successfully, but these errors were encountered: