Skip to content
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

Error Handling Best Practices. #70

Open
xjamundx opened this issue Jan 8, 2014 · 2 comments
Open

Error Handling Best Practices. #70

xjamundx opened this issue Jan 8, 2014 · 2 comments

Comments

@xjamundx
Copy link

xjamundx commented Jan 8, 2014

I've been at PayPal for a few months as part of the move everything to node.js effort. I've noticed that different ideas about how to handle errors in all parts of our app has led to some weird errors and huge problems. We've ended up with some conventions that I think will be helpful to share with other people going through similar transitions and others getting up to speed with node.

We'll discuss things like why try/catch is such a bad idea in async code, decent ways to handle errors in sync APIs, how & why to create custom Error objects, and a friendly reminder to mostly use The Callback Pattern™.

I'll probably be showing lots of terrible code that was found in production. Hopefully it will be a good laugh and informative for people.

@alessioalex
Copy link

👍

1 similar comment
@mstuart
Copy link

mstuart commented Jan 10, 2014

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants