Google-cloud-node: Should our promises be documented as first class?

Created on 17 Oct 2016  路  4Comments  路  Source: googleapis/google-cloud-node

Continuing https://github.com/GoogleCloudPlatform/google-cloud-node/pull/1697#discussion_r83665859:

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.

core p2
Source
picture stephenplusplus

Most helpful comment

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

picture SimenB on 18 Oct 2016
👍8

All 4 comments

/cc @jgeewax @omaray @jmdobry

callmehiphop picture callmehiphop on 17 Oct 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

SimenB picture SimenB on 18 Oct 2016
👍8

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

eoogbe picture eoogbe on 12 Aug 2017

I am no longer on the team

eoogbe picture eoogbe on 2 Feb 2021
Was this page helpful?
0 / 5 - 0 ratings

Related issues

hvolschenk picture hvolschenk  路  4Comments
ddunkin picture ddunkin  路  3Comments
dsimmons picture dsimmons  路  4Comments
jmdobry picture jmdobry  路  3Comments
nicolasgarnier picture nicolasgarnier  路  4Comments