Skip to content

[RFC] Deprecate promise progress API #32

Closed
Closed
[RFC] Deprecate promise progress API#32
Labels
BC break
Milestone
v3.0.0

Description

@clue
clue
opened on Jun 30, 2015

This ticket serves as a basis for discussing deprecating the promise progress API.
This has come up quite a few times.

As a first step, this ticket aims to only deprecate the existing functionality and update the documentation accordingly. At a later stage, we should consider dropping the functionality altogether (BC break ahead).

Opening this ticket as an RFC and for the reference.

Activity

  1. jsor commented on Jun 30, 2015

    @jsor
    jsor
    on Jun 30, 2015
    Member

    References of JS promise libraries deprecating the progression API:

  2. jsor
    modified the milestone: on Sep 7, 2015
  3. jsor
    added this to the milestone on Jan 21, 2016

  4. jsor commented on Jan 21, 2016

    @jsor
    jsor
    on Jan 21, 2016
    Member

    I'm planning to remove the progression API for 3.0.

  5. clue commented on Jan 22, 2016

    @clue
    clue
    on Jan 22, 2016
    MemberAuthor

    👍

  6. jsor
    added a commit that references this issue on Apr 29, 2016

    Remove progression API (closes #32)

    4ab99a6
  7. jsor
    closed this as completedin 4ab99a6on May 3, 2016
  8. clue
    added
    BC break
    on Jun 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    BC break

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions