You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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]
The text was updated successfully, but these errors were encountered:
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.
@laverdetmeteor/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.
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]
The text was updated successfully, but these errors were encountered: