Skip to content

http: deprecate/rename finished in favour of ended #28651

Description

@ronag

What is currently the finished property in http/1 is actually what is ended in the world of streams.

Would it be an idea to deprecate finished (e.g. remove from docs and/or add warning) and add an alias/property called ended instead to better match the streams spec and avoid confusion?

Activity

  1. changed the title [-]http: deprecate finished in favour of ended alias[/-] [+]http: deprecate/rename finished in favour of ended[/+] on Jul 12, 2019
  2. Trott commented on Jul 13, 2019

    @Trott
    Member

    @nodejs/http @nodejs/streams

  3. mcollina commented on Jul 14, 2019

    @mcollina
    SponsorMember

    I'm in favor of a doc-deprecation.

  4. ronag commented on Jul 14, 2019

    @ronag
    MemberAuthor

    @mcollina I assume that means that you are not in favor of adding a ended getter?

  5. ronag commented on Aug 24, 2019

    @ronag
    MemberAuthor

    This has been sorted with writableEnded and writableFinished. Deprecation is separate thing.

  6. added a commit that references this issue on Dec 10, 2019
  7. added a commit that references this issue on Dec 10, 2019
  8. added a commit that references this issue on Jan 14, 2020
  9. added a commit that references this issue on Feb 6, 2020
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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions