Skip to content
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

xmlel vs xmerl records #5

Open
aaronjensen opened this issue May 6, 2016 · 7 comments
Open

xmlel vs xmerl records #5

aaronjensen opened this issue May 6, 2016 · 7 comments

Comments

@aaronjensen
Copy link
Contributor

Hi there, I apologize if I'm missing something obvious, but it looks like fast_xml puts out records that are incompatible with things like xmerl_xpath. Is that intentional? I wasn't able to find anything about xmlel. It'd be great if I could use it as a drop in replacement for xmerl's scan but still be able to use its xpath querying. Thanks!

@aaronjensen
Copy link
Contributor Author

It occurred to me that maybe xmerl was using these other record forms in the past, but isn't now, is that what is going on? Would you be opposed to moving fast_xml to the new record forms for a major version update?

@prefiks
Copy link
Member

prefiks commented May 6, 2016

This library was developed for ejabberd, and i think it was using #xmlel even before xmerl was a thing, so pretty much it's like that for historical reasons.

@aaronjensen
Copy link
Contributor Author

Gotcha, would it be worth moving to xmerl records types for forwards compat? It'd be nice to be able to use it with SweetXml, for example

@prefiks
Copy link
Member

prefiks commented May 7, 2016

I will probably add option to parser functions to change output that would generate xmerl compatible output.

@aaronjensen
Copy link
Contributor Author

That would be great. We use fxml_stream:parse_element/1 so it'd be great if we could pass options to that.

@9mm
Copy link

9mm commented Nov 23, 2018

is there any way i can do xpath with what fast_xml returns?

@zinid
Copy link
Contributor

zinid commented Nov 23, 2018

@9mm no.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants