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.
When the
allowClear
option is enabled and that same component has aonChange
callback, clicking the clear icon will cause an infinite loop. The root cause seems to be thatthis.el.val()
returnsnull
when previously set to an empty string, which is what happens when the input is cleared. As expectedshallowEqualFuzzy
returnsfalse
when comparingnull
to''
which causes an infiniteonChange
callback loop.The new
fuzzyValuesEqual
method returnstrue
whencurrentValue
isnull
andnewValue
is equal to an empty string, otherwise it callsshallowEqualFuzzy
which was the previous behavior.I've also updated the examples with a select2 component set to
allowClear
which can be used to manually test the new behavior. Let me know if there is anything you'd like me to change. Thanks! 😄