Your courses are always great. I started web dev with react but the first name I learned about Angular from your courses on plurasight made me switch to Angular since 2020 and I never regret it. Thanks so much for those content
while it is experimental, the amount of DX on it is awesome. I remember using a subscription to toggle off the loader, but this seems even more easy to implement.
Yep! I *really* like the features they've incorporate into resource/rxResource. One missing feature is to have a initial value so we don't need the extra line with the computed setting up the initial value. I understand that's on the team's todo list.
A dublagem para portugues me ajudou demais, excelente video, conteudo muito util. Trabalho com Angular a 6 anos e de la pra ca sempre estou aprendendo e me atualizando.
Thank you! An interceptor may be better if you have lots of HTTP calls and want to have the same loading indicator for all of them. Otherwise, using this isLoading property is a great way to display the loading indicator.
I guess it would be nice if the resource API exposed a numerical progress value as opposed to an isLoading boolean. That way we could introduce a progress bar, like some websites do.
Hi Deborah, I follow you step by step to modify the code, but I don't understand why doesn't appear the 'Loading...' only ... loading vehicles' that is write in the html template
The first "...Loading" message comes from Stackblitz. Are you using Stackblitz or some other editor? (It's basically irrelevant for the code we are writing. I just pointed it out because it appears when using Stackblitz. Sorry for the confusion.)
I didn't even know that this flag is in the object itself. I usually deal with loading mechanics inside the interceptors. Turning the flag on when requests go out then toggle the flag when the response comes back. This technique is even better because I can control which events I'm interested in. With the interceptors, I need to filter some requests. Let's say when the Oidc -client library wants to check whether the user is still logged in, I should ignore it. Otherwise, the skeleton will appear on the page.
Yes, this feature is very useful! And yes, is much better than manually handling the loading flag in an observable pipeline. An interceptor may be better if you have lots of HTTP calls and want to have the same loading indicator for all of them. Otherwise, using this isLoading property is a great way to display the loading indicator.
That is very kind of you to ask! Currently, I only have one course on Pluralsight: "RxJS and Angular Signals Fundamentals". Thought it's currently over 1 year old and doesn't have the latest signal features. The other Pluralsight courses have been retired. Pluralsight would no longer allow me to update the "Angular: Getting Started" course. ☹ If you are learning Angular from scratch, you could still start with the "Angular: Getting Started" for the basic concepts. Then move on to my "Angular Topics" playlist for more information on newer features: th-cam.com/play/PLErOmyzRKOCr07Kcnx75Aqh6PWSbIokPB.html All the best on your learning journey!
Adding a delay to the resource feels like bad practice. I understand the issue of loading too fast, but what if the client has a slow connection. Then the long time would be increased artifically and worsen UX instead of improving it. I feel like behavior like that might be better suited for the loading bar component
Yeah, no. The delay() is only for use during testing so *we* can see the loading indicator. Immediately after adding the delay in the video, I said: " Be sure to remove any code like this before deploying!"
Your courses are always great.
I started web dev with react but the first name I learned about Angular from your courses on plurasight made me switch to Angular since 2020 and I never regret it.
Thanks so much for those content
That is so very kind of you to say. Thank you!
Glad you are a part of the Angular community. 😊
thank you for the amazing content as always!!
I'm glad you found it useful! Thanks! 😊
while it is experimental, the amount of DX on it is awesome. I remember using a subscription to toggle off the loader, but this seems even more easy to implement.
Yep! I *really* like the features they've incorporate into resource/rxResource. One missing feature is to have a initial value so we don't need the extra line with the computed setting up the initial value. I understand that's on the team's todo list.
Muchas gracias por usar el doblaje automático.
Espero que se traduzca bien para ti. ¡Gracias por mirar!
A dublagem para portugues me ajudou demais, excelente video, conteudo muito util. Trabalho com Angular a 6 anos e de la pra ca sempre estou aprendendo e me atualizando.
Fico feliz em saber que a dublagem funciona bem para você. Tudo de bom! 😊
As always an amazing content, thks a lot. Is interceptor still the best way to display a loader ?
Thank you!
An interceptor may be better if you have lots of HTTP calls and want to have the same loading indicator for all of them. Otherwise, using this isLoading property is a great way to display the loading indicator.
I guess it would be nice if the resource API exposed a numerical progress value as opposed to an isLoading boolean. That way we could introduce a progress bar, like some websites do.
Awesome
Thanks!
Hi Deborah, I follow you step by step to modify the code, but I don't understand why doesn't appear the 'Loading...' only ... loading vehicles' that is write in the html template
The first "...Loading" message comes from Stackblitz. Are you using Stackblitz or some other editor?
(It's basically irrelevant for the code we are writing. I just pointed it out because it appears when using Stackblitz. Sorry for the confusion.)
@deborah_kurata Ah ok now is clear. When I use Stack blitz, appear but when download the code and use VSCode I don't see it 🙂
I didn't even know that this flag is in the object itself.
I usually deal with loading mechanics inside the interceptors. Turning the flag on when requests go out then toggle the flag when the response comes back.
This technique is even better because I can control which events I'm interested in. With the interceptors, I need to filter some requests. Let's say when the Oidc -client library wants to check whether the user is still logged in, I should ignore it. Otherwise, the skeleton will appear on the page.
Yes, this feature is very useful!
And yes, is much better than manually handling the loading flag in an observable pipeline.
An interceptor may be better if you have lots of HTTP calls and want to have the same loading indicator for all of them. Otherwise, using this isLoading property is a great way to display the loading indicator.
@deborah_kurata thank you so much
And I bet the next video is going to be about error handling with rxResource! The world wouldn't be itself if it didn't expose us to errors ;-)
I have a list and error handling is definitely on it! 😊
@@deborah_kurata please upload the video of error handling with rxResource/resource
Yay! We got a yay!
🎉🎉😊
could you please give me courses path for your courses on pluralsight ♥
That is very kind of you to ask! Currently, I only have one course on Pluralsight: "RxJS and Angular Signals Fundamentals". Thought it's currently over 1 year old and doesn't have the latest signal features.
The other Pluralsight courses have been retired. Pluralsight would no longer allow me to update the "Angular: Getting Started" course. ☹
If you are learning Angular from scratch, you could still start with the "Angular: Getting Started" for the basic concepts. Then move on to my "Angular Topics" playlist for more information on newer features: th-cam.com/play/PLErOmyzRKOCr07Kcnx75Aqh6PWSbIokPB.html
All the best on your learning journey!
Hello teacher 🎶 hello teacher 🎶how are you 🎶 how are you 💙💜💛
I am doing well thanks 🎶 I am doing well thanks 🎶
All the best! 🎶 All the best! 🎶
Adding a delay to the resource feels like bad practice. I understand the issue of loading too fast, but what if the client has a slow connection. Then the long time would be increased artifically and worsen UX instead of improving it. I feel like behavior like that might be better suited for the loading bar component
Did you miss the part where she said: "don't do this in production code"?
@richarddefortune1329 okay yeah lmao. xD
Yeah, no. The delay() is only for use during testing so *we* can see the loading indicator. Immediately after adding the delay in the video, I said: " Be sure to remove any code like this before deploying!"