Skip to content

Should our promises be documented as first class? #1699

Closed
Closed
Should our promises be documented as first class?#1699
Assignees
bcoe
Labels
corepriority: p2Moderately-important priority. Fix may not be included in next release.

Description

@stephenplusplus
stephenplusplus
opened on Oct 17, 2016

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.

Activity

  1. stephenplusplus
    added
    docs
    core
    on Oct 17, 2016

  2. callmehiphop commented on Oct 17, 2016

    @callmehiphop
    callmehiphop
    on Oct 17, 2016
    Contributor

    /cc @jgeewax @omaray @jmdobry

  3. SimenB commented on Oct 18, 2016

    @SimenB
    SimenB
    on Oct 18, 2016
    Contributor

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

  4. jmuk
    added
    priority: p2Moderately-important priority. Fix may not be included in next release.
    Type: Enhancement
    Status: Acknowledged
    on Mar 7, 2017

  5. evaogbe commented on Aug 11, 2017

    @evaogbe
    evaogbe
    on Aug 11, 2017
    Contributor

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

  6. evaogbe
    closed this as completedon Aug 11, 2017
  7. JustinBeckwith
    assigned
    evaogbe
    on Feb 1, 2021

  8. evaogbe commented on Feb 2, 2021

    @evaogbe
    evaogbe
    on Feb 2, 2021
    Contributor

    I am no longer on the team

  9. evaogbe
    removed their assignment
    on Feb 2, 2021
  10. JustinBeckwith
    assigned
    bcoe
    on Feb 2, 2021
  11. miguelvelezsa
    added 2 commits that reference this issue on Jul 23, 2025

    chore!: migrate gax to Node 18 (#1699)

    f28f99c

    chore(main): release gapic-tools 1.0.0 (#1713)

    c0558c3
  12. sofisl
    added a commit that references this issue on Feb 25, 2026

    chore: release 5.15.5 (#1699)

    1406ca1
  13. GautamSharda
    added a commit that references this issue on Mar 11, 2026

    chore: store nodejs build artifacts in placer (#1699)

    d6b6b10
  14. sofisl
    added 2 commits that reference this issue on Mar 17, 2026

    chore!: migrate gax to Node 18 (#1699)

    7e30b15

    chore(main): release gapic-tools 1.0.0 (#1713)

    1b35240
  15. thiyaguk09
    added a commit that references this issue on Mar 18, 2026

    chore: release 5.15.5 (googleapis#1699)

    813d673
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

corepriority: p2Moderately-important priority. Fix may not be included in next release.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions