Thank You, content and editing looks too good.. few questions.. 1. 00:07:03 - This syntax looks different than what we usually see in Vue community,, what it is ? 2. 00:07:03 - Looks like you are not registering these local components in App.vue, still it works without any issues.. how it happens ? 3. Finally, how about creating another folder for skeletons rather than keeping them in components folder.. share your opinion for large-scale projects.. Thank you once again !!
Hey! Thanks for the kind words. The answer to your first 2 questions is the same. The Vite template (at least right now), is using an experimental feature with where your whole script essentially acts as the setup method, and everything is auto exported. It's still an active RFC that you can read here: github.com/vuejs/rfcs/pull/227 As for the the last question, I think that's definitely a solid option to have a skeleton folder that mirrors your component's folder. There are definitely some other options such as just using custom directives in the component's themselves and writing a custom renderer to handle skeletons, but for simplicity and precision, the idea you suggested sounds great.
i'm not sure what you mean. are you talking about setting up auth? because i just do that in the supabase console...i've been looking into ways to automatically pass the current supabase user to prisma queries github.com/prisma/prisma/issues/5128#issuecomment-921179713 this looks promising, but haven't tried it yet
Hi, I'm a bit struggled. How can I add more users and photos? I mean this is only one, but if I need three of this with different photos, how I can add it to the code?
Great information but especially the coding part is WAY too fast if you're new to the subject or if you actually want to code along (even with pausing the video).
i think suspense cleans it up because in our setup method, we have an asynchronous component. if we made it a synchronous component and used a v-if, we'd need a helper method to load the data.
Thanks for the video, I have found it interesting, but man, that styling part... its like from 2010... You have mentioned responsive design, than you set min-height, and started to float things around... maybe its just me, but I find this discusting... (I'm a front-end dev). Don't get me wrong the meaningful part of this video is fine, but the styling part is unnecessary and quite bad.
The best Vue blog I've found, now with videos... fantastic 😁
Thanks! Can't wait to keep making awesome Vue content for you all 😃
Great video! Didn't even know Suspense components existed before today, and now I have a good understanding of how to use them
Great video! You're explanations are always so clear
Thanks for your support - it really means a lot.
To the point tutorial, really helpful. Thanks man
Nicely done! Moves along at a good clip, good post-production, kudos!
This is very useful and can increase the user experience
God bless you man, I love your channel and your website.
Thank you for this beautiful solution ❤️❤️
Thank You, content and editing looks too good.. few questions..
1. 00:07:03 - This syntax looks different than what we usually see in Vue community,, what it is ?
2. 00:07:03 - Looks like you are not registering these local components in App.vue, still it works without any issues.. how it happens ?
3. Finally, how about creating another folder for skeletons rather than keeping them in components folder.. share your opinion for large-scale projects..
Thank you once again !!
Hey! Thanks for the kind words.
The answer to your first 2 questions is the same. The Vite template (at least right now), is using an experimental feature with where your whole script essentially acts as the setup method, and everything is auto exported. It's still an active RFC that you can read here: github.com/vuejs/rfcs/pull/227
As for the the last question, I think that's definitely a solid option to have a skeleton folder that mirrors your component's folder. There are definitely some other options such as just using custom directives in the component's themselves and writing a custom renderer to handle skeletons, but for simplicity and precision, the idea you suggested sounds great.
@@LearnVue Thank You !!
Man you are beast. Keep doing that please. Good job
Cool, it helps to create the vue page.
glad you think so!
that's super but can you use tailwind css with the same example
Videos with Tailwind will be coming in the near future :)
This is cool and much more nice looking!
i'm not sure what you mean. are you talking about setting up auth? because i just do that in the supabase console...i've been looking into ways to automatically pass the current supabase user to prisma queries github.com/prisma/prisma/issues/5128#issuecomment-921179713 this looks promising, but haven't tried it yet
Great video. Thank you!
Why use a span if you’re just going to convert it to a div with block display?
with vue router?
Hi, I'm a bit struggled. How can I add more users and photos? I mean this is only one, but if I need three of this with different photos, how I can add it to the code?
isnt a good idea to set the height of the skeleton line to 1em or even 1ch as its inherinting the font stiles from the original card?
Quality content.
Nice
Awesome awesome video!
how to create custom animation every time onscroll page
This video should not have this less amount of like
Did you see the animation of the skeleton? I didn't
can i use this with laravel?
Goat
Great information but especially the coding part is WAY too fast if you're new to the subject or if you actually want to code along (even with pausing the video).
why not just use a v-if on data wherenver it is loaded
i think suspense cleans it up because in our setup method, we have an asynchronous component. if we made it a synchronous component and used a v-if, we'd need a helper method to load the data.
Thanks for the video, I have found it interesting, but man, that styling part... its like from 2010... You have mentioned responsive design, than you set min-height, and started to float things around... maybe its just me, but I find this discusting... (I'm a front-end dev). Don't get me wrong the meaningful part of this video is fine, but the styling part is unnecessary and quite bad.
too much useless blah-blah-blah and style descriptions.