DEV Community

Discussion on: Vue: When a computed property can be the wrong tool

Collapse
716green profile image
Bob Bass

This is an excellent article. I'm going from memory here but I could swear that some Vue components I've built in the past always seemed one tick behind where they were supposed to be.

I'm pretty sure that I've had to use watch() to fix the problem but I might also be conflating a slightly different issue with this.

Either way, this was really interesting and I'm glad that you took the time to write about it.

I switched from Vue to React within the past year or so for many of my personal projects and so I've been out of the loop a little bit, but I just took a job working with Vue. I feel like I've missed so much in the past few months. I was still using the options API with Vue 3 and without a setup directive and then I saw Vitesse.

Vue is such an awesome framework.

Collapse
linusborg profile image
Thorsten Lünborg Author

Glad you found it helpful.

the issue you describe sounds like it's not related to what I am describing here. Lazy evaluation won't cause any timing issues.

Also, don't feel pressures to use setup() if you feel comfortable with Options API - i won't disappear or anything.