Details
-
Type:
Feature Request
-
Status: Open
-
Priority:
L3 - Default
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: frontend, Single Instance
-
Labels:None
-
Epic Link:
Description
Feature description
When the user expands a parent flow node instance and then scrolls, we should load more of the child instances first, before loading instances on the parent level
Solution draft
Scrolling down
- Load the next 50 instances on the deepest (currently visible) expanded instance by leveraging pageSize and searchAfter params of the flow-node-instances API
- To make this work we need to determine which instance (on which level) is the last element in the list
Scrolling up
- Load the next 50 instances on the deepest (currently visible) expanded instance by leveraging pageSize and searchBefore params
- To make this work we need to determine which instance is the first element in the list