Listing the troubles with the SweetXpath modifiers #88
Description
I'm listing here the github issues regarding the behavior of the modifiers.
As a lot of information is lost between the call of xpath/xmap, the internal call of :xmerl_xpath.string, and the final result, a lot of issues have been raised, and some merge requests have been proposed.
At the moment, I am not able to conceive a "peaceful" path of evolution. The library has a lot of cruft, and the recent evolutions regarding security, while remaining backward compatible, contribute negatively to the usage of the library. People wanting to benefit from them must put in more effort to bring restrictions, while I believe the effort for the user should be when we want relaxed security.
So I tend to want go toward a new set of API, but that's no different from an entirely new version, aka a new library.
Anyway, the main topic:
#62
#53
#37
#23
#20
#14
#10
#8
#4
#87
#80
#72
#70
#33 (to dig)
#30
#17
Considering the timeline of the merge requests, it feels understandable that the modifiers evolved to the current state.
I'll see if I have the time in the coming weeks to formalize the needs around this feature.