fix(select): prevent defaulting to first option when no value selected #3690
+6
−2
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
Fixes #3198
This PR updates the hidden input inside the
Select
component to handle caseswhere no option is selected.
Changes
value={value}
tovalue={value ?? ""}
in the hidden input""
)instead of
undefined
or defaulting to the first optionBefore
When a
<Select>
was rendered with no value selected, the hidden input coulddefault to the first option’s value, causing forms to submit an unintended result.
After
If no value is selected, the hidden input now submits an empty string (
""
),allowing form submissions to correctly reflect that no selection was made.