You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provide a non function to the bind utility method.
What is expected?
In <= 2.5.13, it rendered but failed silently: https://jsfiddle.net/ujxu9mvd/. Not sure if we'd want to keep that expectation, but existing projects will fail to render completely. A dev-mode warning at the very least will be helpful in identifying the issue.
What is actually happening?
Uncaught TypeError
The refactoring of the bind method to use the native bind, exposes a coding error when upgrading from 2.5.13. We have a fairly large codebase and one of the developers mistakenly added an object as a component method (eg. a global Vue events instance). It made its way into production and worked fine until upgrading to 2.5.14. It took a while to find it as there was no clear indication as to where the error was happening.
Some other devs experienced this as well: #7491 324672a
The text was updated successfully, but these errors were encountered:
Version
2.5.14
Reproduction link
https://jsfiddle.net/bad4a8mb/1/
Steps to reproduce
Provide a non function to the
bind
utility method.What is expected?
In <= 2.5.13, it rendered but failed silently: https://jsfiddle.net/ujxu9mvd/. Not sure if we'd want to keep that expectation, but existing projects will fail to render completely. A dev-mode warning at the very least will be helpful in identifying the issue.
What is actually happening?
Uncaught TypeError
The refactoring of the
bind
method to use the native bind, exposes a coding error when upgrading from 2.5.13. We have a fairly large codebase and one of the developers mistakenly added an object as a component method (eg. a global Vue events instance). It made its way into production and worked fine until upgrading to 2.5.14. It took a while to find it as there was no clear indication as to where the error was happening.Some other devs experienced this as well:
#7491
324672a
The text was updated successfully, but these errors were encountered: