-
-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
fix(runtime-dom): v-model breaks minlength validation #1937
Conversation
Why not just compare the 2 values? The less involved the better performance. |
some biased performance tests misled me. it's my fault. 😭 |
🤐I have not processed a |
next !== prev || | ||
(hostForcePatchProp && hostForcePatchProp(el, key)) | ||
(hostForcePatchProp && hostForcePatchProp(el, key)) || | ||
next !== prev |
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.
Why do you change this order? Typically a compare operation would be lighter than a method invoke. It's reasonable to have the comparison ahead.
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 you are right. I think I should learn more about javascript optimization.
https://jsben.ch/dSVTE
more detail: #1935 (comment)
close #1935