A terrible thing happened. You actually have the same way of writing as me. My last problem was that there were two exactly the same options, and one was usable and the other was not. So it is not recommended that you use this method.
Use watch to monitor your value. If it changes, call the event to be data-driven.
@change="" is also possible, but there are definitely limitations.
Same as method 1, except that in other places where you use this value, you also use the variables tied to your v-model to be data-driven, but it also has limitations and it is impossible to use it in all scenarios
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
The click event is written in <select>
A terrible thing happened. You actually have the same way of writing as me. My last problem was that there were two exactly the same options, and one was usable and the other was not. So it is not recommended that you use this method.
Use watch to monitor your value. If it changes, call the event to be data-driven.
@change="" is also possible, but there are definitely limitations.
Same as method 1, except that in other places where you use this value, you also use the variables tied to your v-model to be data-driven, but it also has limitations and it is impossible to use it in all scenarios