Add deprecation warning DEP0066 by mroderick · Pull Request #24167 · nodejs/node (original) (raw)

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 andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation30 Commits2 Checks0 Files changed

Conversation

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters

[ Show hidden characters]({{ revealButtonHref }})

mroderick

This PR makes the deprecation for DEP0066 an active deprecation in code.

Hello from NodeConfEU 👋

Checklist

@addaleax addaleax added semver-major

PRs that contain breaking changes and should be released in the next major version.

code-and-learn

Issues related to the Code-and-Learn events and PRs submitted during the events.

labels

Nov 6, 2018

@addaleax

BridgeAR

@mroderick

I don't understand why the linter would fail in this case, and the error is a bit odd to me:

/home/travis/build/nodejs/node/.eslintrc.js:20
    } catch {
            ^
SyntaxError: Unexpected token {

The PR doesn't touch .eslintrc.js. Further, line 20 in .eslintrc.js looks different in my branch:

which shouldn't cause a syntax error. 😕

Any ideas on how to resolve this?

@jasnell

@mroderick... I think that failure may be unrelated to your changes. Will look into it tho

@jasnell

Btw... This error is generally because node.js 8 is being used by the linter...

@targos

trivikr

@mroderick

@mroderick

@Trott

Trott

Trott previously requested changes Nov 13, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

doc/api/deprecations.md needs to be updated to indicate that this is now a Runtime deprecation.

@Trott

@nodejs/tsc This needs TSC approvals if it is to land.

@Trott

@targos

Do we have any idea about ecosystem usage of these properties?

@Trott

@Trott

@mroderick

made the doc change

Thank you. I was going to do that this morning, but you beat me to it 👍

@Trott

This needs @nodejs/tsc approvals and a CITGM run.

@mcollina

@refack

mcollina

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

apapirovski

@mroderick @Trott

Change doc-only deprecation for _headers and _headerNames accessors to a runtime deprecation.

PR-URL: #24167 Reviewed-By: Ruben Bridgewater ruben@bridgewater.de Reviewed-By: Trivikram Kamat trivikr.dev@gmail.com Reviewed-By: Matteo Collina matteo.collina@gmail.com Reviewed-By: Anatoli Papirovski apapirovski@mac.com

@Trott

@Trott

@Trott Trott added the author ready

PRs that have at least one approval, no pending requests for changes, and a CI started.

label

Nov 22, 2018

thefourtheye

Trott pushed a commit to Trott/io.js that referenced this pull request

Nov 22, 2018

@mroderick @Trott

Change doc-only deprecation for _headers and _headerNames accessors to a runtime deprecation.

PR-URL: nodejs#24167 Reviewed-By: Ruben Bridgewater ruben@bridgewater.de Reviewed-By: Trivikram Kamat trivikr.dev@gmail.com Reviewed-By: Matteo Collina matteo.collina@gmail.com Reviewed-By: Anatoli Papirovski apapirovski@mac.com Reviewed-By: Sakthipriyan Vairamani thechargingvolcano@gmail.com

@Trott

Landed in 91748dd.
Thanks for the contribution! 🎉

(If you're interested in other possible contributions to Node.js but don't have a good idea of where to start looking, some ideas are posted at https://www.nodetodo.org/next-steps/.)

@mroderick mroderick deleted the add-deprecation-warning-DEP0066 branch

November 23, 2018 16:46

@mroderick

refack pushed a commit to refack/node that referenced this pull request

Jan 14, 2019

@mroderick @refack

Change doc-only deprecation for _headers and _headerNames accessors to a runtime deprecation.

PR-URL: nodejs#24167 Reviewed-By: Ruben Bridgewater ruben@bridgewater.de Reviewed-By: Trivikram Kamat trivikr.dev@gmail.com Reviewed-By: Matteo Collina matteo.collina@gmail.com Reviewed-By: Anatoli Papirovski apapirovski@mac.com Reviewed-By: Sakthipriyan Vairamani thechargingvolcano@gmail.com

BethGriggs added a commit that referenced this pull request

Apr 22, 2019

@BethGriggs

Notable changes:

PR-URL: #26930

BethGriggs added a commit that referenced this pull request

Apr 23, 2019

@BethGriggs

Notable changes:

PR-URL: #26930

BethGriggs added a commit that referenced this pull request

Apr 23, 2019

@BethGriggs

Notable changes:

PR-URL: #26930

This was referenced

Apr 23, 2019

Reviewers

@Trott Trott Trott left review comments

@apapirovski apapirovski apapirovski approved these changes

@mcollina mcollina mcollina approved these changes

@thefourtheye thefourtheye thefourtheye approved these changes

@BridgeAR BridgeAR BridgeAR approved these changes

@trivikr trivikr trivikr approved these changes

@jasnell jasnell Awaiting requested review from jasnell

@joyeecheung joyeecheung Awaiting requested review from joyeecheung

Labels

author ready

PRs that have at least one approval, no pending requests for changes, and a CI started.

code-and-learn

Issues related to the Code-and-Learn events and PRs submitted during the events.

http

Issues or PRs related to the http subsystem.

notable-change

PRs with changes that should be highlighted in changelogs.

semver-major

PRs that contain breaking changes and should be released in the next major version.