[MGNLUI-6447] Allow custom filters and support limit depth level for JCR datasource related fields Created: 09/Dec/20 Updated: 17/Aug/23 |
|
| Status: | Open |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 6.2.5 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Viet Nguyen | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Template: |
|
||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||||||||||
| Testcase included: |
Yes
|
||||||||||||||||||||
| Documentation update required: |
Yes
|
||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||
| Epic Link: | Datasource filtering | ||||||||||||||||||||
| Description |
|
An example use case is that customer "only want to give the editor the possibility to select categories with a depth of 1, we wanted to write a custom class to filter out categories that have a depth of > 1. But I cannot find the place where I could realize this." Irrespective of the example mentioned above, customer would be generally interested to know at which point they can apply an appropriate filter for similar cases. |
| Comments |
| Comment by Roman Kovařík [ 09/Dec/20 ] |
|
For the record, filtering is limited by JCR query, so far we expose only allowedNodeTypes in the datasource definition. |