This repository has been archived by the owner on Jan 16, 2024. It is now read-only.
FullHierarchy search. Backend query, without descendants option. #403
Labels
Milestone
Comments
AndrewRAM33
added
bug
Something isn't working
enhancement
New feature or request
labels
Aug 17, 2020
AndrewRAM33
pushed a commit
that referenced
this issue
Aug 17, 2020
AndrewRAM33
pushed a commit
that referenced
this issue
Aug 17, 2020
AndrewRAM33
pushed a commit
that referenced
this issue
Aug 19, 2020
AndrewRAM33
pushed a commit
that referenced
this issue
Aug 19, 2020
AndrewRAM33
pushed a commit
that referenced
this issue
Aug 19, 2020
AndrewRAM33
pushed a commit
that referenced
this issue
Aug 19, 2020
AndrewRAM33
pushed a commit
that referenced
this issue
Aug 20, 2020
AndrewRAM33
pushed a commit
that referenced
this issue
Aug 20, 2020
sergromanov4
pushed a commit
that referenced
this issue
Aug 26, 2020
Dergash
pushed a commit
that referenced
this issue
Aug 28, 2020
Dergash
pushed a commit
that referenced
this issue
Aug 31, 2020
DRITE
pushed a commit
to DRITE/tesler-ui
that referenced
this issue
Feb 1, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
FullHierarchy search enhancement.
Feature
Consider ability to exclude descendants from
FullHierarchy
search result.Bug:
During filter operation, backend query is executed, which results is a new data for hierarchy. Thus, search is completely backend-side. Implemented
FullHierarchy
filter algorithm on the frontend side is not used.Bug:
Empty
FullHierarchy
data, when clear existing filter.Bug:
Empty
FullHierarchy
data, when sort will be applyed.The text was updated successfully, but these errors were encountered: