fix(frontend): set experiments table search debounce interval to 600ms#1545
Open
yoganandaness wants to merge 3 commits into
Open
fix(frontend): set experiments table search debounce interval to 600ms#1545yoganandaness wants to merge 3 commits into
yoganandaness wants to merge 3 commits into
Conversation
Junjiequan
reviewed
May 29, 2026
| data={fetchExperimentsData} | ||
| options={{ | ||
| search: true, | ||
| debounceInterval: 100, |
Contributor
There was a problem hiding this comment.
Is debounceInterval: 100 equal to 600ms?
Contributor
Author
|
@copilot get the debounce time to 600ms from 100 |
Contributor
Updated in commit |
jekabs-karklins
approved these changes
May 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Updated the experiments table search debounce interval to
600msin the frontend to align with the intended behavior.Motivation and Context
The experiments table debounce value needed to be standardized to
600msto match expected search behavior and avoid premature search triggering.How Has This Been Tested
cd apps/e2e && npm run lint100, 200, 300, 400, 500, 600) and confirmed the expected behavior pattern for the timing assertion used during verification.Fixes
N/A
Changes
debounceIntervalfor experiments table search inapps/frontend/src/components/experiment/ExperimentsTable.tsx.Depends on
N/A
Tests included/Docs Updated?