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

Should our promises be documented as first class? #1699

Closed
stephenplusplus opened this issue Oct 17, 2016 · 4 comments
Closed

Should our promises be documented as first class? #1699

stephenplusplus opened this issue Oct 17, 2016 · 4 comments
Assignees
Labels
core priority: p2 Moderately-important priority. Fix may not be included in next release.

Comments

@stephenplusplus
Copy link
Contributor

Continuing #1697 (comment):

Should we be promoting promise use first, as in "this is the way to use our library", with a mention about callbacks? Since the demand for promises is so strong, I'm wondering if we might be better off changing our position to a promise library that supports callbacks instead of the other way around.

@callmehiphop
Copy link
Contributor

/cc @jgeewax @omaray @jmdobry

@SimenB
Copy link

SimenB commented Oct 18, 2016

As a complete outsider, I vote yes!
Especially with async await on the horizon, it's a way better way of writing async code

@jmuk jmuk added priority: p2 Moderately-important priority. Fix may not be included in next release. Type: Enhancement labels Mar 7, 2017
@evaogbe
Copy link
Contributor

evaogbe commented Aug 11, 2017

This issue may no longer be relevant due to its age. Feel free to re-open.

@evaogbe
Copy link
Contributor

evaogbe commented Feb 2, 2021

I am no longer on the team

@evaogbe evaogbe removed their assignment Feb 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core priority: p2 Moderately-important priority. Fix may not be included in next release.
Projects
None yet
Development

No branches or pull requests

6 participants