-
Notifications
You must be signed in to change notification settings - Fork 55
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
Use node-style callbacks throughout #38
Comments
+1 |
So, yes, how does one detect errors at all? |
Or, you could expose promises and allow user to hook into success and failure callbacks. BTW, you also throw exceptions in the code in some callbacks, this is not a good pattern because it can kill the whole server. |
+1 If an error happens, this library does kill my app regularly. |
+1 Considering using |
Pull request (#43) issued with proposed fix. I'm also considering removing the support for promises from nodemw. |
Callbacks should be passed an
Error
as the first argument and data as the second.Like so:
Instead of:
The text was updated successfully, but these errors were encountered: