Open aaronjensen opened 8 years ago
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?
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.
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
I will probably add option to parser functions to change output that would generate xmerl compatible output.
That would be great. We use fxml_stream:parse_element/1
so it'd be great if we could pass options to that.
is there any way i can do xpath with what fast_xml returns?
@9mm no.
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 aboutxmlel
. 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!