Improve resetting values when using the nullable
prop on the Combobox
component
#2660
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.
This PR fixes a bug where clearing out the value of the
Combobox.Input
didn't always reset the value properly.We will now make sure to:
nullable
mode goes back to the previous optionnullable
mode, after the input has been cleared doesn't go to any optiononChange
(React) or@update:modelValue
(Vue) is being called withnull
when a reset happens (this is important for you to reset a potentialquery
value for filtering purposes)One gotcha is that typically you reset the
query
for filtering in theonChange
/@change
of theCombobox.Input
. However, when pressing escape the value is cleared but theonChange
/@change
won't be fired because it is cleared programmatically and not by the end user.To solve this, you can use the following snippet to ensure that the
query
is still being cleared when the value changes tonull
:React:
Vue:
Fixes: #2433