-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
(fp/no-nil) rule for callbacks? #43
Comments
oh yes, you can't use callbacks because by their nature they're not pure |
Yeah just a lot of code has this convention and wanted the ruling on it. I will try to use promises instead of callbacks. |
I'd recommend using some effects library like Monet or IxJS then converting to a promise or continuation passing API at the last possible moment. |
promises are also impure! |
Yeah I have separated side effects from my functions in my codebase but at the end it has a callback. |
It is standard to write callbacks with error first so you end up with
callback(null, "success message")
orcallback(err)
.Is the solution to get around this to not use callbacks?
The text was updated successfully, but these errors were encountered: