-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
View Matcher #3609
Comments
This OTOH, |
That's a dangerous question because it will lead to very challenging design process, to find the common, generic and extensible part. And once we find it and implement it, then it may turn out that Schema or Matcher needs features which stretch that generic concept too much :D. So, as I don't see a close resemblance, I'm all for coding them independently. We'll have more freedom and it will be faster. |
Yeah, that was my second thought too, still I wanted to share that there is something similar between them. I agree to code them independetly. |
I think that it is aways a good direction to create specific solution, find the common part and export it to the generic solution, if you it find useful. Creating very generic solution at the begging usually lead to the code which is very hard to maintain. |
Additional matcher feature may be handling wildcards ( |
It should be possible to check if node or list of nodes match given pattern or list of patterns.
The pattern should be build once for every match:
It should works for the list of elements:
It should handle list of rules:
It should handle callback, for example to check children of the element:
The text was updated successfully, but these errors were encountered: