You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apex-XPath supports a simple core of XPath 1.0 syntax. I think it occupies the sweet spot between simplicity and comprehensiveness. It's simple enough to cover maybe 95% of your use cases directly. For the other 5%, Apex-XPath takes you close enough that you can finish filtering the results with minimal effort by using the standard Dom.Document & XmlNode classes.
So far it has covered 100% of my use cases, but I want to know if there are any features of XPath you've found yourself wishing it would support directly. Is there anything we could add to it that would greatly simplify your projects? Or should we keep the library nice & simple, and anything more would just give us diminshing returns of needless complexity?
The text was updated successfully, but these errors were encountered:
Thanks for getting back to me on this. I did play around with the count approach you mention. In the end I went for a simpler solution than XPath syntax: XPath was great for engineers but tough for the intended configuration people.
Apex-XPath supports a simple core of XPath 1.0 syntax. I think it occupies the sweet spot between simplicity and comprehensiveness. It's simple enough to cover maybe 95% of your use cases directly. For the other 5%, Apex-XPath takes you close enough that you can finish filtering the results with minimal effort by using the standard Dom.Document & XmlNode classes.
So far it has covered 100% of my use cases, but I want to know if there are any features of XPath you've found yourself wishing it would support directly. Is there anything we could add to it that would greatly simplify your projects? Or should we keep the library nice & simple, and anything more would just give us diminshing returns of needless complexity?
The text was updated successfully, but these errors were encountered: