One thing I really appreciate is how thorough you are with the explanations. I always wondered how to type the action errors, in my case typescript always complains if there is a return null and return json({ error: “hey” }) it complains that error is non existent and I always have to do return json({ error: null }) and return json({ error: “hey” })
Great video! One asthetic suggest I would offer is to have the text in the app that is rendering be much larger and easier to read. I'm watching this vid on my 50" tv and can't see very well. In gengeral, I would take a little time to ensure that even your dummy data screens are somewhat pleasant/satisfying to look at. Some big fat text and some padding could go a long way here. Info in the vid is top notch, just a "cherry on top" suggestion.
Thank you so much for the constructive feedback, I'll try to make it better in the future, I've also noticed that after rewatching the video. I started a new series so will try to make everything look as good as possible!
@@alemtuzlakyou don't need to go crazy. Just some satisfyingly larger with some padding and maybe a container with mx: auto so it's not left justified on a wide monitor will go a long way.
Very nice tutorial ❤... when 'throw redirect' is there a way to show toast messages to user ?? How do I send that "toast messages" from loader and action
hi! Great video! Im having a problem where I have error boundries defined but any server error just crashes my local dev server and I have to restart the server everytime with npm run dev. Any tips?
If I remember correctly it should always be undefined as you might use it somewhere where the Loader data is not available (eg you try to access /products loader data on /articles page) so a good practice is to check if the data is there and throw otherwise with a warning you're using the hook somewhere where you shouldn't
Very nice tutorial..its good that you use diagrams to teach. Loved it. Actually learnt what serialization is :)
Thank you so much, so happy to hear that!
Thanks for the extension
Thank you!
One thing I really appreciate is how thorough you are with the explanations. I always wondered how to type the action errors, in my case typescript always complains if there is a return null and return json({ error: “hey” }) it complains that error is non existent and I always have to do return json({ error: null }) and return json({ error: “hey” })
Thank you so much! Well the easiest way to make typescript happy with this is to do const error = "error" in actionData ? actionData.error : null;
@@alemtuzlak thanks!!! will try it out :)
Amazing as always!
Thank you!
Great video! One asthetic suggest I would offer is to have the text in the app that is rendering be much larger and easier to read. I'm watching this vid on my 50" tv and can't see very well.
In gengeral, I would take a little time to ensure that even your dummy data screens are somewhat pleasant/satisfying to look at. Some big fat text and some padding could go a long way here.
Info in the vid is top notch, just a "cherry on top" suggestion.
Thank you so much for the constructive feedback, I'll try to make it better in the future, I've also noticed that after rewatching the video. I started a new series so will try to make everything look as good as possible!
@@alemtuzlakyou don't need to go crazy. Just some satisfyingly larger with some padding and maybe a container with mx: auto so it's not left justified on a wide monitor will go a long way.
gd one thx
No worries!
Very nice tutorial ❤...
when 'throw redirect' is there a way to show toast messages to user ??
How do I send that "toast messages" from loader and action
Thank you! You can check out remix-toast to see how you can do that
hi! Great video!
Im having a problem where I have error boundries defined but any server error just crashes my local dev server and I have to restart the server everytime with npm run dev. Any tips?
Thank you! Are you using a custom server or the remix one?
Hi Alem, If i add an error boundary to the root, useRouteLoaderData Hook is becoming undefined. Is there a way to tackle this?
If I remember correctly it should always be undefined as you might use it somewhere where the Loader data is not available (eg you try to access /products loader data on /articles page) so a good practice is to check if the data is there and throw otherwise with a warning you're using the hook somewhere where you shouldn't