I like the early/late word framing! Is there still time to rename the directives to "use earlier"/"use later" 😜
I like the early/late word framing! Is there still time to rename the directives to "use earlier"/"use later" 😜
When conductimg interviews I try to remove as many obstacles as possible (eg trying to make them feel relaxed) so they can perform their best. To that end, I make it clear upfront that I want them to talk through their thoughts process even if they don't finish the assignment
Accurate 😂
"dimalmighty: The Coding Enigma Wrapped in a Bluesky Mystery"
blueskyroast.com
Starting in 19, you shouldn’t need to fetch in an effect for any of these use cases.
Initial GET should be cached and read in render with use().
Refresh GET should clear the promise cache to trigger with use() again.
POST/PUT/DELETE mutations should be done in event handlers with actions.
A comic featuring Mario & Link. Mario gives Link a mushroom and jokes that he will be ‘hyperlink’. Link eats it and turns blue, gives Mario a high five then turns purple
🍄🔗
Via: www.lightroastcomics.com
Switch statements and for loops
Interesting bee-skeet 🍪😅
@react.dev @ricky.fm @danabra.mov (apologies if I violate tagging etiquette)
React experts help! Say I have a component that accepts a ReactNode as a prop (not children). Is it valid to use React.Children to get the prop component's children? Use case being setting different layout depending on that component having children or not