[MGNLUI-5807] JCR Data provider filtering bugs/improvements Created: 08/Apr/20  Updated: 06/May/20  Resolved: 08/Apr/20

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

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 1h
Time Spent: 58m
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-5671 Make sure Filters are in enabled in a... Closed
causality
is causing MGNLUI-5806 Possible performance issue while filt... Closed
documentation
to be documented by MGNLUI-5847 DOC: JCR component filtering Closed
supersession
supersedes MGNLUI-5765 Chooser filters don't work in tree view Closed
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Documentation update required:
Yes
Epic Link: M6 UI & UX Improvements
Sprint: UI Framework 21
Story Points: 0

 Description   
  • node name search is supported, but column might actually show jcrName property which can contain invalid characters. This might give an impression filtering doesn't work
    • filter by 王芳 Wang Fang in personas app
    • no results as the real node name is ---Wang-Fang
  • list view filtering by path /travel/about matches /sportstation/about as well
  • hierarchical filtering works only for content of folders (filtering pages filters out all items which parent doesn't match, so it's not really possible to filters deeper items)


 Comments   
Comment by Roman Kovařík [ 14/Apr/20 ]

Column filtering

Jcr data provider supports column filtering

  • column name = property name to filter by
  • column filter value = property value to filter by
  • special column filtering
    • Filtering by jcrTitleColumn matches node name or jcrName property
    • Filter component of jcrStatusColumn filters by activation status
    • Filtering by jcrPath column filters by node path

Tree view filtering

  • Item is not filtered out if the item itself of any of its children matches the filter.
    • this might have a performance impact for items with thousands of sub nodes
      • depending on how fast do you expect filtering to be, you might want to
        • provide only list view 
        • or not provide filter components in your custom apps for huge workspaces
        • disable filter components by decorating out of the box apps (pages)
                filterComponent:
                  $type: hiddenField
                

 

Filter object is shared between list and tree view.

Therefore same filter components should be available in both views (except for jcrPath which is expected to be only in list view and ignored in the tree view).

Otherwise the filter would be applied but not visible in the other view.

 

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