Replacing to okgrow:promise should we update our current promisses?

[deanrad]

Replacing to okgrow:promise should we update our current promisses?

[jrudio]

Just a heads up, moving to okgrow:promise took away server-side Meteor.promise.

[deanrad]

yes, @jrudio - on the server, Meteor.call doesn't require a callback, running synchronously in a fiber - so having a Promise for it in the server seemed redundant.

[deanrad]

@ssoulless - No veo ningún razón porqué no funcionaran. Why don't you try it and see ? The only thing you may notice is if you rely on the toString() version of a Promise, which has changed. Other than that - just renaming and additional APIs that's all :)

[jrudio]

Thanks @deanius, I feel dumb for using it like that on the server.
haha

[deanrad]

@jrudio ha 👍

[ssoulless]

Thanks Just for let you know, I just replaced this package for the new one, I was afraid of make my app crash, or have to update promises markup, however everything kept working in the normal fashion, so you can update with confidence =)

[deanrad]

Thanks for the report @ssoulless !