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
We have a bug in our code that results in an undefined partial name for a split second. This causes a TypeError to be thrown before assertAsset can display a meaningful warning. fiddle
The problem is that resolveAsset assumes that the asset id will be a string, even though this is not necessarily the case when the id is dynamically bound. A few possible solutions:
Force the asset id to a string before camelization
Only perform camelCase and PascalCase lookups if isString(id)
Assert that the asset id is a string, although all calling code would now have to handle that case. Partial/component/other asset registration would probably need to do the same as the following is technically legal: Vue.partial({}, '<div>lolol</div>'
The text was updated successfully, but these errors were encountered:
We have a bug in our code that results in an undefined partial name for a split second. This causes a TypeError to be thrown before
assertAsset
can display a meaningful warning. fiddleThe problem is that
resolveAsset
assumes that the asset id will be a string, even though this is not necessarily the case when the id is dynamically bound. A few possible solutions:isString(id)
Vue.partial({}, '<div>lolol</div>'
The text was updated successfully, but these errors were encountered: