I just opened the video and watched few sections and i am impressed with the way you teach and just saw the views, felt bad this video deserves more views
*Thank you,* for making these video tutorials Explanation was so simple & crystal clear. I have a doubt, Sir what can be done if external API used is currently down, its not good if user keeps going from pages to pages as everything will show error occurred. How can we shift in maintenance mode or something like that ?
You are most welcome! Yes we can and we can do it in the error.js file itself… say if your back-end is throwing an error saying the maintenance going on, you can get that as part of the error argument in the error.js file. Based on that error message or code you can show a component that says, Maintenance mode on… You can do this on per widget/page or you can also catch it as a global error to show it on the main page. In that case, you should have a global error page co-located to the top-level layout. I hope it is clear now.
@@Beast80K I'll make a video on error handling in depth soon… but before that a big one coming tomorrow that we must know before we know any other topic from Next.js. Stay tuned 😀
I just opened the video and watched few sections and i am impressed with the way you teach and just saw the views, felt bad this video deserves more views
Thank you! Regarding the reach of the videos, yeah hope it grows 😀
Crytal clear Parallel Routes, Great!!!
Many thanks!
Thank you sir
Thank you so much! You are always been extremely supportive to tapaScript 👍
So much value in a 30mins long video. Kudos to your efforts.
Glad you liked it! ❤️
Outstanding presentation vai. ekta intercepting routes niye cai eibar. now it is very clear to me. Thank you very much Tapash vai.
Thank you ❤️
yes I learnt something new Thank You..
Great, I am glad.
BEST EXPLANATION
Thank you
thanks dada
Most welcome
*Thank you,* for making these video tutorials Explanation was so simple & crystal clear.
I have a doubt, Sir what can be done if external API used is currently down, its not good if user keeps going from pages to pages as everything will show error occurred. How can we shift in maintenance mode or something like that ?
You are most welcome!
Yes we can and we can do it in the error.js file itself… say if your back-end is throwing an error saying the maintenance going on, you can get that as part of the error argument in the error.js file.
Based on that error message or code you can show a component that says, Maintenance mode on…
You can do this on per widget/page or you can also catch it as a global error to show it on the main page. In that case, you should have a global error page co-located to the top-level layout.
I hope it is clear now.
@@tapasadhikary Respected Sir, thank you once again, if possible you may make a video on this topic, as it will be helpful for beginners.
@@Beast80K I'll make a video on error handling in depth soon… but before that a big one coming tomorrow that we must know before we know any other topic from Next.js. Stay tuned 😀
If Nextjs don't know the parallel routes, how it will know default.js file present in that parallel routes.
so nice dada
You are most welcome, Swapon 👍
Every time I shifted from a route group to another route group my page is reloading. Is it possible to prevent the reloading ? thanks in advance
I need to see the code, the default behavior is no reloading.
what's the cricket bat about!
It is a gift from a dear friend... It looks good, right? 😀