-
Notifications
You must be signed in to change notification settings - Fork 96
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
Bugfix/gh782 acl xml format #793
Conversation
Or maybe I'd open this against 1.4 branch? |
Agree. > 1.4 |
Yes, let's try and get this into 1.4.5. |
%% these types should be defined in xmerl.hrl or xmerl.erl | ||
%% for now they're defined here for convenience. | ||
-type xmlElement() :: #xmlElement{}. | ||
-type xmlText() :: #xmlText{}. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
xmlElement
and xmlText
should be exported types (thanks dialyzer)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is fixed in #795
Reopened an issue against release/1.4 => #795. |
The root cause for #782 was misuse of
xmerl_scan:string/2
, which doesn't emit spaces, comments between actual xml elements. It leaves them as#xmlText{}
and#xmlComment{}
- This pull request commit changes to ignore them at walking around parsed dom tree.This diffset also includes a small refactoring that wraps all
xmerl_scan:string/2
to oneriak_cs_xml
funcsion to control its usage.