I know this is a couple weeks old but at 1:34:11 for the typescript search -a rams possibly null error, you just need to do optional chaining to fix it
How is using parallel routes different from using a traditional layout.tsx for the nav and a page for the content? Can't data be fetched in the layout to get the team's info, instead of making it a parallel route and then render the traditional single page.tsx? Just trying to wrap my mind around that more advanced approach.. thank you btw, this livestream is a goldmine
Did I understand correctly the scenario with server actions returning JSX? The server action would return JSX and on the client side we would push it into a state, and then pull out it out during rendering of the component?
![[FULL EP.73] เปิดบ้าน 70 ล้าน "แป้ง Zbing" ยกมาทั้งญี่ปุ่น l เคหสถานบานปลาย l One Playground](http://i.ytimg.com/vi/YBnJhTt07Pg/mqdefault.jpg)
Please do a video about caching. In depth. Explain everything. This is the part everyone struggles with.
th-cam.com/video/VBlSe8tvg4U/w-d-xo.html
Hey, Lee!
Could you please add video timings?
I know this is a couple weeks old but at 1:34:11 for the typescript search -a rams possibly null error, you just need to do optional chaining to fix it
you need an api route for downloading files too, cant be done via server actions
How is using parallel routes different from using a traditional layout.tsx for the nav and a page for the content?
Can't data be fetched in the layout to get the team's info, instead of making it a parallel route and then render the traditional single page.tsx?
Just trying to wrap my mind around that more advanced approach.. thank you btw, this livestream is a goldmine
Did I understand correctly the scenario with server actions returning JSX? The server action would return JSX and on the client side we would push it into a state, and then pull out it out during rendering of the component?
youtube stream is back
My theme One Dark pro darker looks so grayish compared to this 😩