ฝัง
- เผยแพร่เมื่อ 2 ต.ค. 2024
- Prop stability is an important concept in Vue. By eliminating unnecessary updates, we can improve the performance of our app.
✅ FREE VUE 3 CHEATSHEET WITH ESSENTIAL CODE SNIPPETS
learnvue.co/vu...
follow me on twitter:
/ mattmaribojoc
🚨 Like quick Vue lessons like these? Check out 800+ lessons over on Vue School - go.learnvue.co...
Music by Lukrembo - Storybook
I would like to see more "best practices" videos!
This example is based on the one from the docs. Just read the docs.
your Vue videos are top tier. super helpful, intuitive, concise, and interesting. thank you and please keep it up!!!
Oh my god this is the type of stuff I nerd over please more tips like that! Great video 👍
Beyond any doubt this is one of your most useful videos :)
It’s not that easy to run into recommendations like this, so I would really appreciate it if you could share some more best practices with us
And as always, thank you! :)
Thank you. Simple yet very important concept. Adding to my checklist "prop stability analysis"
Amazing! Do you have a discord channel?
i've been thinking of making one...you interested?
@@LearnVue Yes! Would be really appreciated!
Great video!! thanks
I like this short kind of tips/tutorials. It is easy to watch.
Great. Indeed useful. Making videos like this will improve your subscribers very soon. Good luck and keep posting useful videos like this.
Sir please make a video.... How to bundle vue3+ with django
Hi, thanks for video! I really like you channel.
There is a siren sound in the theme, and I never pay attention to it, till this war. So interesting how human noticing different things
No, i'm definitely not following this practice, until now...
Tks dude! 😄💥
I've started learning vuejs a few weeks ago and this channel helped me a lot!
gl
I've stopped stopped liking your videos after watching them, I just press play, like and get wowed, you never disappoint and that's just the honest truth.
Can we have an A.I. model that'll go through your codebase & find this kind of inefficiency???
Amazing. I am just creating an image gallery that I know will hugely benefit from this knowledge. Thank you so much for sharing 🙂
I would like to see more "best practices" videos!
I would like to see more "best practices" videos!
Woooo
That’s funny because I literally made this mistake and codepen was throwing an error on my code ! (Vs code wasn’t)
Quality content. Loved it.
Much appreciated!
Insightful
Great!
Fireship tone clone :)
Instructional ++
Basicaly just pass the minimum amount of data
I would like those type of videos
Didn't notice that before. Helps a lot! Thank you!
That's actually a nice tip. I really like this one
Like your short and very informative videos
This is great! Thanks for sharing.
Awesome video! Thanks a lot
Is this code editor vs code?
Scary but powerful
How about an Object prop ? Does it trigger an update if the children component mutate the value of an attribute of the Object prop ?
Great video btw 😄
more videos like this please
Im gonna start doing this
makes perfect sense
Great video!!
super helpful 🥰
Simple and effective!
Thanks!
Does the component also rerender when a bound attribute is changed that the component does not define as a prop? For example when binding $attrs to a child.
Why would it?
@@dvdrtrgn It's a reactive property bound to the component just like a prop
@@UBERDHOKER So only if the attr has a reactive value bound will a rerender be triggered upon an $attrs change.
Amazing tip.
Glad you think so!
This is actually a bad practice. The component should be written so that they do not update if not needed. The issue of the solution mentioned in the video is that it moves logic out of the component....
How would you go about this? Could you provide an example?
@@joseisrael2946 sorry, I do not remember this exact issue and do not have time to rewatch it now. All I remember is thar he duplixates some part of the logic out of the component to detect if the component should be updated And that is totally against the idea of compobents - packing all related code, logic, etc at one place.
If you ever need to change the logic, you should be doing it only in the component. Only if the component need more inputs or its output changes only then you should need to go out of the component.
One general solution could be that the component would have some sort of method "do I need to be updated?".
Why Vue is so esoteric and complicated.
Welcome to my pages 🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰🥰
Thanks for this:
activeId=(activeId+1) % arr.length