fix(select): remove code causing excessive calls to the onValueChange prop #2063
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.
TASK: #2062
Description, Motivation and Context
While using the
Select
component in controlled mode, two issues have been observed:onValueChange
prop is executed on initial render, even though the value has not been changed.onValueChange
prop is executed twice.Repro ➡ https://stackblitz.com/edit/stackblitz-starters-ulfsq2?file=pagesContent%2Findex.tsx
The problem seems to originate from
packages/components/select/src/SelectContext.tsx
, specifically this piece of code:The weird thing is, when we comment out what's inside the
useEffect
, all the tests still pass. And even when we interact with the component in the browser (in both controlled and uncontrolled modes), it doesn't seem to break anythingTypes of changes