-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Call cb if provided to send even if callOnError was true #44
Comments
@anandthakker could you write a quick patch for this? I think it'll make more sense once I see it - Main use case for passing Perhaps a possible solution would be to call |
@yoshuawuyts yep, see ^. My use case here is that I want to use |
Ah, but so at the top level Does that make sense? |
@anandthakker is this still an issue? Any way I can assist? |
Ah -- I've managed to move along okay without it, but it's sometimes Why do I have effects that need a synchronous "send"? Because I'm actually On Mon, Jul 18, 2016 at 8:27 AM Yoshua Wuyts [email protected]
|
If I've created a
send
withcreateSend('blah', true)
-- so that errors go to the store'sonError
handler -- I might also want to use send asynchronously. @yoshuawuyts what do you think about including anif (cb) { cb(err) }
at the end ofonErrorCallback
(L131 on master)?The text was updated successfully, but these errors were encountered: