This is to ease the writing of UIs to edit properties for XPath rules specifically (eg the designer).
The current utility to maintain the mappings from XPath property type ids to property extractors (PropertyDescriptorUtil) gives out very little info on the descriptors that each type id build, which makes it necessary to hardcode behaviour in the designer. It would be more convenient for everyone to have an enum, instead of a bare map, the constants of which can be enriched with other relevant info.
This can be considered a follow-up on #758, #736, and somewhat related to #504, though I see no reason to schedule it for 6.0.0. The simplest is probably to tackle this along with #762.
Sorry @adangel, these changes should really have been appended to #758...
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4