ui: Remove old style 'filterable' searching #9356
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our old style searching was based on an asynchronous based component (ChangeableSet) where you would pass a 'filterable/searchable' to it and it would use that filterable/searchable to perform the searching. This has now been entirely replaced with
DataCollection
component that follows a similar approach but can perform all types of 'Collection' type tasks on a collection/array of data - so searching, filtering and sorting.The final things to be replaced were searching/filtering/sorting of
upstream-instances
and also searching/sorting of our 'ChildSelector' component which is used for selecting Roles and Policies whilst creating tokens and namespaces, which we switch out here.There is still a tiny bit of work to go on the
DataCollection
component, but I started adding a README file here for it in order to document out its properties a little, and I'll probably fill it out a little more once its complete.