fix: Redundant CollectionListViewProvider
#163
Closed
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.
…text` search value.
Why did you create this PR
CollectionListViewProvideris redundant aftercustom-list-pagerender theListView.useTableStatesContextreturn the wrongsearchvalue, it must bedebouncedSearch.useSearchused to explicit return the internal search value state, now it returnsprops.search,props.onSearchif user provided.What did you do
CollectionListViewProvideruseTableStatesContextreturn correctsearchvalieuseSearchreturn the user defined controlled valuepagestopagein list UI configChecklist