-
Notifications
You must be signed in to change notification settings - Fork 24
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
RMPathQuery matchSpecialisedNodes #448
Conversation
Codecov ReportBase: 71.34% // Head: 71.38% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #448 +/- ##
============================================
+ Coverage 71.34% 71.38% +0.03%
- Complexity 6723 6735 +12
============================================
Files 657 657
Lines 22254 22276 +22
Branches 3573 3578 +5
============================================
+ Hits 15877 15901 +24
Misses 4680 4680
+ Partials 1697 1695 -2
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Also add tests for Archetype.item(s)AtPath(IncludeSpecialised)()
Adds matchSpecialisedNodes variable to RMPathQuery, which makes it possible to specify a path to return all specialised nodes as well.
For example: if an RM object of a specialisation of an archetype contains values of node id's 5.1 and 5.0.1 then creating an RMPathQuery with matchSpecialisedNodes = true and a query pointing to "id5", and then calling findList() (or find() but then only one result) would result in returning both the 5.1 and 5.0.1 objects.