Really appreciate the great feedback! Very glad you like it! 😊

Haha can't win! If we do light people complain, if we do dark people complain 😅 Noted though, I'll probably intermix some light themes in every once in a while. Maybe just randomize it each episode 😉

Thanks for the kind words and feedback! 1. Noted, I'm still trying to figure out the best layout. I don't want to cut off any of my screen recording, but unfortunately to keep our faces up there I have to scale the screen down just a bit. So basically theirs a blank space either way that I need to fill with something, so I figured a title at least keeps the context for folks viewing in full screen. I'm open if you have another suggestion on what to put down there! 2. Yep, good point, thanks! That code is the starting point, not the finished product we built together. I'll update the description to reflect this

@@ReactTipsWithBrooksAs someone who studied videography as well I feel that I can’t give advice on editing, everyone is unique in their own way, except when it comes to the code, the font needs to be a bit bigger😂 And I totally understand on the whitespace, dont be afraid to zoom in on your faces.

@@yarapolana Thanks so much for the tips! I'll definitely be sure to bump the font size more in future recordings (hopefully the next one is already good). I'll play around with zooming in on our faces a bit more too to see if I can squeeze some more room. Thanks again!

How?

Yep, that could work too, thought it's not necessarily more web-like than using a cookie (cookies have been around for quite a while and are very web-like). The reason I personally wouldn't take that approach is because you have a lot more fiddling to do with the query params. You'll need to remove the query params once the notification is dismissed, and if there are other query params you do want you need to make sure they stick around. A bigger problem though is if someone shares the link with the query param, now anyone who goes to that link is going to see a random toast notification, which would probably be pretty confusing. You could protect against this by looking up the session information for the user, but then at that point you're already back in cookie land essentially.

that's a bad, working approach

@@C0ntenTT Are you replying to me or OP? In either case, would you care to elaborate why you think it's a bad approach?

@@ReactTipsWithBrooks Replying to OP, not you. and the reason is exactly what you mentioned

Thanks for elaborative answer here! Much appreciated@@ReactTipsWithBrooks

Note: I don't want to submit a form programmatically with timeouts on a component level

I would use useSubmit to submit a post request to clear the cookie after the duration or when the toast unmounts

Yep, you could definitely use SSE. Personally I think that'd be a bit of overkill just for a simple toast notification. You'd also have to setup a unique channel for each user, since you don't want to share the notification to multiple users accidentally. You'd also likely want to cleanup the emitter as soon as you're done using it, since a toast notification is generally pretty fire-and-forget. If you had a stream of notifications/messages you want to give a user, then SSE might make sense in that case

@@ReactTipsWithBrooksYou are right and after some more digging not all browsers are compatible so SSE is not worth all that engineering. Thank you for answering. Didn’t know you had a personal channel I just subscribed 🎉

Thanks @@yarapolana! I'm not super active on it at the moment, hopefully will get back to it more at some point