Nathanaël

Hi, is it relevant to keep this open ?

The main problem (from memory), is that `:xmerl_xpath.string/3` [1] either returns a list, or a scalar (without information on whether the xml path is unreachable) that is wrapped in a...

> So if xmerl doesn't provide information on whether the path is reachable for strings This part needs testing, as this is simply my inference from what the type of...

```elixir @spec subspec_map(subspec, (%SweetXpath{} -> %SweetXpath{})) :: subspec when subspec: (%SweetXpath{}| keyword(%SweetXpath{} | subspec)) def subspec_map(%SweetXpath{} = x, transform) do transform.(x) end def subspec_map({k, x}, transform) do {k, subspec_map(x, transform)}...

Hi, so it's confirmed that we won't do breaking changes, and we will go the path of documenting thoroughly the modifiers in order to leave no surprises to the users

Hi @kephas, have you also encountered this problem ? xmerl is part of OTP (as can be seen here: https://erlang.org/doc/applications.html, and here: https://github.com/erlang/otp/tree/master/lib/xmerl). I suggest checking your erlang installation to...

Alright, if I understand better your earlier comment, we need to improve the readme and the documentation to ask the user to ensure that his installation of erlang was done...

Thanks, I'll keep the issue open for a bit as a reminder for myself to see how I deal with this and the doc for https://hexdocs.pm/

Hi, what version of reaxt is this using ? We need to do an up to date version as it is pretty old and behind by a few major versions.

I just tried building it and on recent versions of elixir the plug dependency is so old that it doesn't compile :\