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
proxyConsole.js:72[Vuewarn]: Propertyormethod"$_testMixin_testData"isnotdefinedontheinstancebutreferencedduringrender.Makesurethatthispropertyisreactive,eitherinthedataoption,orforclass-basedcomponents,byinitializingtheproperty.See: https://vuejs.org/v2/guide/reactivity.html#Declaring-Reactive-Properties.foundin---><TestMixin> at /src/App.vue
<Root>
What is expected?
It's expected for the prop to be defined
What is actually happening?
The prop is undefined if the variable contains symbols in the beginning
I am not completely sure if this is a bug or intended, since I think it is a bug I opened this issue, yet if this is intended the error shown should be giving more details, it took me some time to understand what was the error because it isn't clear just from the error message.
The text was updated successfully, but these errors were encountered:
Properties that start with _ or $ will not be proxied on the Vue instance because they may conflict with Vue’s internal properties and API methods. You will have to access them as vm.$data._property.
And still the error message is not comprehensible, the developers should be able to fix this problem without reading the whole docummentation, in other words I think a better error message would be more appropriate.
Version
2.5.17-beta.0
Reproduction link
https://codesandbox.io/s/r0lr534k94
Steps to reproduce
Open the console and see the error:
What is expected?
It's expected for the prop to be defined
What is actually happening?
The prop is undefined if the variable contains symbols in the beginning
I am not completely sure if this is a bug or intended, since I think it is a bug I opened this issue, yet if this is intended the error shown should be giving more details, it took me some time to understand what was the error because it isn't clear just from the error message.
The text was updated successfully, but these errors were encountered: