This repository has been archived by the owner on Aug 21, 2024. It is now read-only.
Enabled use of client pagination in FeathersHook useFind #9128
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.
Summary
Since we can enable
paginate:false
for certain services usingenableClientPagination
hook on server end. But there was an issue in FeathersHook on client as it was appending those pagination limit, step, etc variables which was overriding the request to not handlepaginate: false
.🤖 Generated by Copilot at ebdd973
Modified
useFind
hook to support non-paginated queries. The hook now checks the query parameters forpaginate
or$paginate
flags and passes them to theuseService
hook accordingly.References
closes #insert number here
Explanation
🤖 Generated by Copilot at ebdd973
useFind
hook to handle non-paginated queries (link)🤖 Generated by Copilot at ebdd973
QA Steps
List any additional steps required to QA the changes of this PR, as well as any supplemental images or videos.
Checklist