-
-
Notifications
You must be signed in to change notification settings - Fork 33.9k
fix #6193, change event should not be triggered if each value still matches an option #6194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
e90d6d1 to
d9b2f41
Compare
change event should not be triggered if still can found matching option for each value
| } | ||
| } | ||
|
|
||
| function hasNoMatchingOption (value, options) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how about Array.prototype.some or every😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it would be better to use [].some.
Actually I just did revert changes made in c90b140, and didn't think about that. 😅
Will do it later.
|
Is it released ? |
|
It hasn't been merged yet, so: no. |
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
devbranch for v2.x (or to a previous version branch), not themasterbranchfix #xxx[,#xxx], where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information:
#6193
It seems we still need the value matching check, only detect options change is not enough.