-
Notifications
You must be signed in to change notification settings - Fork 237
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
Switch to more standardish/expected callback(error, data) pattern #23
Comments
Please please please! I was pulling my hair out trying to figure out why my callback logic wasn't executing, only to find out it only executes when there's an error. @desmondmorris This wouldn't be hard to implement. Should I file a P/R? |
👍 Its def time for this. @sedge go for it! We should probably track these changes against a new branch, 1.x. We can work towards a better callback pattern, test coverage and code standards. |
Will do. I was wrong about when the callback logic fires - user error 😦 |
Node standard is callback(err, data), and this patch updates the code to reflect this.
👍 |
1 similar comment
👍 |
👍 I am starting to flesh a roadmap for a general cleanup of this library. This will be top of th is list https://github.com/desmondmorris/node-twitter/wiki/1.x-Roadmap |
@bryanburgers @sedge @fuchse @despairblue - A new callback pattern has been added to v1.x. Give it a spin. See https://github.com/desmondmorris/node-twitter/blob/master/README.md for details |
It would be nice if the library used the standard callback pattern.
The text was updated successfully, but these errors were encountered: