[MGNLUI-6055] Allow user to add predicates by configuration to JcrDataProvider Created: 20/Jul/20  Updated: 17/Aug/23  Resolved: 10/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.2
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Evzen Fochr Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: ui-devx-impr
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-6208 Provide more flexible datasource filter Open
relates to ABTEST-250 Hide variants or disable editing them... Closed
relates to MGNLUI-6447 Allow custom filters and support limi... Open
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)
Date of First Response:
Epic Link: UI framework implementation

 Description   

Actual state:
info.magnolia.ui.contentapp.HierarchicalJcrDataProvider#getChildren
have hardcoded list of 3 items : NodeTypeFilteringPredicate, PropertyFilteringPredicate and ActivationStatusFilteringPredicate

Improvement:
Allow user to add his own more complex predicate, aka filter by parent nodetype etc. by configuration



 Comments   
Comment by Roman Kovařík [ 01/Sep/20 ]

The title is talking about JcrDataProvider (list), but description about HierarchicalJcrDataProvider (tree).

Using a predicate in JcrDataProvider is possible but inefficient (ideally it should use plain JCR queries).

Generated at Mon Feb 12 09:32:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.