-
Notifications
You must be signed in to change notification settings - Fork 3
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
XML read/write is not idempotent #41
Comments
Aliaksei-Tatarynchyk
added a commit
to Aliaksei-Tatarynchyk/shaper
that referenced
this issue
Apr 2, 2019
Aliaksei-Tatarynchyk
added a commit
to Aliaksei-Tatarynchyk/shaper
that referenced
this issue
Apr 2, 2019
- fix test data
Aliaksei-Tatarynchyk
added a commit
to Aliaksei-Tatarynchyk/shaper
that referenced
this issue
Apr 2, 2019
- comment test until the issue will not be fixed fully
Aliaksei-Tatarynchyk
added a commit
to Aliaksei-Tatarynchyk/shaper
that referenced
this issue
May 27, 2019
- fix CI - change write bytes to just write to be able to write string
Aliaksei-Tatarynchyk
added a commit
to Aliaksei-Tatarynchyk/shaper
that referenced
this issue
May 27, 2019
- fix test data - fix CI - change write bytes to just write to be able to write string - comment test until the issue will not be fixed fully
arno49
pushed a commit
that referenced
this issue
May 27, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Shaper currently converts xml into yaml with errors, it doesn't able to distinguish child elements and attributes. E.g. if we have the following xml:
It will be converted to yaml:
Output xml after writing this yaml will be:
It's drastically different. Also it ignores DTD declaration, e.g. if to put
<!DOCTYPE rest-security SYSTEM "dynamosystemresource:/atg/dtds/rest/restSecurity_1.0.dtd">
it will not appear in yaml.I'd suggest as quick fix - to change parser mapping for .xml files from XMLParser to TextParser. In this case the yaml will be:
And the output xml will be identical to the initial one.
The text was updated successfully, but these errors were encountered: