Like if you ever "lost" reactivity!

I really like your videos because they are close to real life problems. Another big topic is avoiding losing reactivity with arrays.

The timing of this video is crazy. I was literally wrapping a prop in a ref and was wondering why my code was not behaving correctly. This video explanation was really helpful. Thank you for creating such an informative short video.

When the video came out, I watched and said to myself 'meh, it's a rare case'. Here coming back after spending more than an hour debugging my code. What a life haha! Thanks, Alexander!

Wow, excellent video, some of this stuff can be really confusing and isn't (AFAIK) really explained in the docs either - at least not as a whole. It's also great that you make recommendations "in passing" such as "don't destructure props" - addressing common mistakes before they happen is a great idea :-). Really a must-watch video IMHO, thanks for making it :-)

Thanks for explaining this very simply, Alexander. I especially liked all the different options because you've hit the different cases I personally used. Please keep up with this type of content. I appreciate it a lot!

Thanks Alex, please keep it up! I see every single video

I'm French. Your content is so qualitative! Thank you so much!

Your tutorials are very good! Would you be able to create a tutorial for writing a composable that could accept a primitive, ref, or getter? Or at least a deep dive into how vueuse or the nuxt composables handle this scenario?

high value videos -some of the best most consice vue/nuxt content out there

Thanks covering this, love it when you show common pitfalls! Even with vue experience I keep making some of these :)

After working on react for 2 years , now moving to vue and it just amazed me. But now react making huge change by bringing its compiler hope that it wont hurt vue. Xd :) Btw, Good content.

Nice tutorial! Also caution for times that objects are being passed in a component, the reactivity mechanism can end up being based on value by reference. More examples and best practices of such cases could be interesting.

Thabk you this solved my problem. Realle good videos, keep it going this ir helpful in many ways 😊😊

I must say, awesome content! keep going great, Alexander!

Is there any overhead if we would use toRefs() compared of toRef() ? I do prefer using toRefs() and destructing that result. But I wonder if there is overhead due to it parsing all props instead just the ones you want to make reactive. Or is this negligible?

I didn't know props is "reactive()" under the hood, nice! I'm surprised you didn't mention making a computed of title in the component. What's your stand here? It works, but probably not recommended?

Would a computed() value work the same as toRef()?

Great explanation Alex! Made complete sense!

This solves a lot of my problems 😂.

Which title will be considered in template, props.titile or toRef(...)

Thanks a lot

nice information not many people talk about this simple but important concept.♥♥♥

probably i should read docs, but the obvious question is: what’s the difference between computed and toRef? why didn’t you use computed? and instead used toRef?

Thanks, Alex 💚

An Other great video ty Alex

🔥🔥

Wonder if we ever gonna get a simpler ref vs reactive | useFetch vs $fetch. Its not very intuitive for most beginners.

Thank for the video, really useful. I wonder is there a way to use somehow toRefs to not lose reactivity?

Exactly.... We shouldn't destructuring the props 💯, i used to do in my initial days🤦😂

auto import is not quite good. other devs will have a headache debugging or reading the code.

the .value thing is so annoying sometimes :/

I think you're left-handed 5:10