Property xxx was accessed during render but is not defined on instance

Vue3. X version is used in combination with element plus. If you use form elements and V-model commands, you will see similar warnings on the console. Although it does not affect JS operation, it is hard for obsessive-compulsive disorder players. Let’s take a look at how this problem is generated and how to solve it

In vue3. X, a new composite API, namely the setup method, is added. In this method, we can create a data with a responsive basic data type through Ref. however, we can also set the ref attribute to the element to obtain dom. Please refer to the official documents for details, This also leads to the problem
I believe most people just want to know what the solution is. Look down at the solution
to ensure that the data of V-model and the value of ref do not have the same name
avoid using V-model when you do not need to use V-model (of course, this method is a bit of bullshit)
this method is a little bit of nonsense  


Read More: