-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UISACQCOMP-233: add useDebouncedQuery
hook to fix endless request for DynamicSelection
component
#834
Conversation
…amicSelection` component
useDebouncedQuery
hook to fix endless request for DynamicSelection
componentuseDebouncedQuery
hook to fix endless request for DynamicSelection
component
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sonar is cranky about the lack of tests for useDebouncedQuery
, and I think we have a CPM gotcha in there too. These issues need to be resolved.
My only other comment is that useDebouncedQuery
is a generic name for the slightly more specific work that is happening in this hook. Maybe provide a default do-nothing implementation of dataFormatter
as well if you want to keep this name?
Some documentation would be helpful too since returning the debounced input-setter as setInputValue
, while clever, is not obvious at first glance.
Everything else looks good.
Quality Gate passedIssues Measures |
…or `DynamicSelection` component (#834) * UIF-562: add `useDebouncedQuery` hook to fix endless request for `DynamicSelection` component * test: fix failing tests and update changelog file with correct Jira ticket number * test: add test coverages * refactor: rename hook outputs and add default formatter
Purpose
UISACQCOMP-233: add
useDebouncedQuery
hook to fix endless request forDynamicSelection
componentApproach
Screen.Recording.2024-11-25.at.17.55.10.mp4
Pre-Merge Checklist
Before merging this PR, please go through the following list and take appropriate actions.
If there are breaking changes, please STOP and consider the following:
Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment. Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.
While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.