-
-
Notifications
You must be signed in to change notification settings - Fork 307
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
Failure to recognize xml attributes without whitespace (but with line breaks) #350
Comments
I'm glad you find this repository helpful. I'll try to address your issue ASAP. You can watch the repo for new changes or star it. |
You should have a space more than a |
Yeah the point of this issue is to point out that the parser doesn't support attributes that are separated using line breaks (as in it'll treat it as part of the tag) Which seem to work differently from some other parsers which accepts line breaks as a way of separation (tested on Java's XML parser, and some IDE's syntax highlights like IntelliJ and Visual Studio Code) I personally am not sure if it's part of the specification to support this format, or those parsers are just being lenient about it. Also, the above code is a simplified XML of what users may upload to my site, so technically I would have to manually fix their XML (or reject it), if it's formatted this way |
Thanks. @ttu-ttu . We can probably consider it as a feature request this time. and check later if this is really needed. |
done in v4 |
This is a major which required a bunch of changes. The reason for the bump is the fix for NaturalIntelligence/fast-xml-parser#350 which solves the bug, but there are also a lot of additional bugfixes. Also had to copy some code from the SF E2E utils to the UT utils to get the linter to stop complaining about the TS scope.
This is a major which required a bunch of changes. The reason for the bump is the fix for NaturalIntelligence/fast-xml-parser#350 which solves the bug, but there are also a lot of additional bugfixes. Also had to copy some code from the SF E2E utils to the UT utils to get the linter to stop complaining about the TS scope.
This is a major which required a bunch of changes. The reason for the bump is the fix for NaturalIntelligence/fast-xml-parser#350 which solves the bug, but there are also a lot of additional bugfixes. Also had to copy some code from the SF E2E utils to the UT utils to get the linter to stop complaining about the TS scope.
This is a major which required a bunch of changes. The reason for the bump is the fix for NaturalIntelligence/fast-xml-parser#350 which solves the bug, but there are also a lot of additional bugfixes. Also had to copy some code from the SF E2E utils to the UT utils to get the linter to stop complaining about the TS scope.
This is a major which required a bunch of changes. The reason for the bump is the fix for NaturalIntelligence/fast-xml-parser#350 which solves the bug, but there are also a lot of additional bugfixes. Also had to copy some code from the SF E2E utils to the UT utils to get the linter to stop complaining about the TS scope.
This is a major which required a bunch of changes. The reason for the bump is the fix for NaturalIntelligence/fast-xml-parser#350 which solves the bug, but there are also a lot of additional bugfixes. Also had to copy some code from the SF E2E utils to the UT utils to get the linter to stop complaining about the TS scope.
This is a major which required a bunch of changes. The reason for the bump is the fix for NaturalIntelligence/fast-xml-parser#350 which solves the bug, but there are also a lot of additional bugfixes. Also had to copy some code from the SF E2E utils to the UT utils to get the linter to stop complaining about the TS scope.
This is a major which required a bunch of changes. The reason for the bump is the fix for NaturalIntelligence/fast-xml-parser#350 which solves the bug, but there are also a lot of additional bugfixes.
Description
fast-xml-parser does not treat attributes separated by (only) line breaks as attributes.
Input
Code
Output
expected data
Would you like to work on this issue?
Bookmark this repository for further updates.
The text was updated successfully, but these errors were encountered: