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

Option to throw the exact error returned in callback #206

Closed
totty90 opened this issue Jan 20, 2015 · 2 comments
Closed

Option to throw the exact error returned in callback #206

totty90 opened this issue Jan 20, 2015 · 2 comments

Comments

@totty90
Copy link

totty90 commented Jan 20, 2015

I have errors with more information than just a string and I would like to make it work with fibers. Currently my input can be {message: 'My Message', code: 'someCode'} and the fibers just gives me [object Object]

@laverdet
Copy link
Owner

Meteor is doing some fancy serialization stuff which causes some lost information. meteor/meteor#2774 is the relevant issue there. @mitar had a solution that could make this work in #144, but I'd have to do some testing and tweaking there.

@estark37
Copy link

@laverdet meteor/meteor#2774 doesn't have much to do with serialization. (And doesn't have much to do with Meteor at all, I think.) The user is basically noticing that you can't usefully console.log errors that are thrown through futures.

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