Good Morning!
Morning ๐
Morning
morning
mogge
๐
morning
oh wait i already morning'd
mรฅning
UTG protocol permits multiple mornings i think @alex.lynham
phew
morning morning
morning
UTG is idempotent! the RFC says so! (I just decided)
idempotent across what kind of timescales? I typically wish a good people a Good Morrow around 4 times a year; Does that mean I have achieved full coverage?
Is the second one ignored?
you can call it as often as you want and it always has the same result.
That's not strictly true. Saying morning at 8:24am triggers different responses from saying it at 10:11am.
React question;
I've got a table component that does an http fetch and then formats the results; I've just realised that I need to access these results from a new component on the same page
should I fillet out the http/fetch into a third invisable component? I'm not sure how well that would work in React:
React feels a bit more like WIN32 api, everything has to be a window
i don't suppose you have redux or something available where there's a state atom?
no I don't. That would be the proper solution though, wouldn't it
probably overkill at this point though; I might just bump the State Variable into the topmost view and hope for the best
and ponder introducing redux in the medium term
Different response might still have the same result.
(I'm just making this up as we go along)
idk, i think react is fundamentally quite flawed WRT state mgmt and redux is a better model
plus better devtools
you can put the state variable in the topmost view and pass it down using react context which avoids having to pass it through intermediate components
recoiljs is something modern react ish in this space that might be interesting to look at too if you're contemplating redux