try{ console.log('derp') } catch(err){console.log(err)}finally{console.log('yerp')}
emit
an Error
in an eventChannel and then take
from that channel it should throw, right? This doesn’t really work for me. Meaning it just doesn’t throw it seems
put
vs. putResolve
, e.g., so more generally, I'm hoping to find a collection of sequence diagrams or something like that
@trassmann I have a delete acition that calls a confirmation modal that can reject or accept the call. Let's say I clicked delete like five times then clicked no and sixth time clicked yes on the confirmation modal: the generator function calls the API for a delete request (six HTTP requests) - I checked in the network tab in chrome dev tools). It seems to that when clicking "No" the confirmation modal doesn't actually reject the call of the delete generator function.
Danke sehr! :)))
apisauce
for calls to my api server so everything in the requests part is handled very well right now. What I wanted to do is make sure I handle possible scenarios that might happen in the production which cannot be reproduced so well manually. Like what if there's an inconsistent state or what if the data is corrupted or what if something happens on put or call. I need to handle those errors too. I'm not concerned about anything breaking in the UI since I'm having error boundaries for them but I need to make sure everything works fine with sagas too. Right now I pretty much have one try catch block in every saga which kind of feels redundant and doesn't look pretty to me. So I was looking for an elegant way to do that.