-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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 and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc, tls: mark parseCertString() as deprecated #14245
doc, tls: mark parseCertString() as deprecated #14245
Conversation
This is a sub-PR of #14218 (comment). |
/cc @jasnell |
/ping @jasnell |
I assume this is blocked by #14218 to begin with |
@addaleax Why it blocked? And I've rebased the code. As @refack said, it's a sub-PR of #14218. I will split that PR into 3 sub-PRs and this is the first one of them.
|
4387926
to
1def55b
Compare
@nodejs/ctc ... a decision needs to be made whether deprecating this in 8.x is appropriate. |
doc/api/deprecations.md
Outdated
querystring.parse(str, '\n', '=')`; | ||
``` | ||
|
||
*Note*: This function is not completely equivalent to `querystring.parse()`, one |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: Replace comma with a period. One
then will begin a new sentence.
Deprecations are supposed to be semver-major, right? We should stick to that unless there is a compelling user-focused argument otherwise. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with a nit.
Yes, deprecations are semver-major, which means this PR would not be able to land as a backport to 8.x... unless we special case it as we're done in other cases. The question is whether this one rises to the level that a special case needs to be made. I'm not so sure. I signed off because the code change itself looks fine, but I'm not convinced that this should land. |
e9491f1
to
7c3fed5
Compare
@jasnell You mean you're not convinced that it should land in 8.x but it's fine for 9.0.0? Or you mean not land at all? |
Oh, never mind, I see, this is an 8.x-specific PR. Yeah, I'm not sure it should land either. Fine for 9.x...And I'm OK if CTC decides to special-case it, but that really really makes me wonder if we need to revise our deprecation policy because these special cases seem to come up more than I expect them to.... |
Just repeating the observation that
IMHO (3) is reasonable since it's definitely an edge case for deprecation, but not obviously |
I wouldn't stand in the way of a doc-only deprecation. If we can get a clean diff for that, maybe we can ping CTC and take it as consensus if no one objects after 72 hours. |
b95abf4
to
1cb3e56
Compare
/ping @nodejs/ctc |
@nodejs/ctc Any objections to landing this doc-only deprecation in 8.x? It is for a property that was made public by mistake. |
@Trott It seems to me like if we introduce a deprecation in 8.x, we should also deprecate in master so that we don’t accidentally un-deprecate when releasing 9.0.0? |
I think this PR should be landed before #14249. |
If there are no objections from @nodejs/tsc I would land this as a semver-minor. |
/ping @nodejs/tsc |
With no objections by now, I'd say this is likely good to go as a semver-minor |
Landed in 703a3b5 |
`tls.parseCertString()` was made public by mistack. So mark it as deprecated. PR-URL: #14245 Refs: #14193 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: Rod Vagg <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
Thi needs to be backported to v8.x-staging. You can follow the guide and raise a backport PR against |
`tls.parseCertString()` was made public by mistack. So mark it as deprecated. PR-URL: nodejs#14245 Refs: nodejs#14193 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: Rod Vagg <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
`tls.parseCertString()` was made public by mistack. So mark it as deprecated. PR-URL: #14245 Refs: #14193 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Refael Ackermann <[email protected]> Reviewed-By: Rod Vagg <[email protected]> Reviewed-By: Colin Ihrig <[email protected]>
* **crypto** * Support for multiple ECDH curves. [#15206](#15206) * **dgram** * Added `setMulticastInterface()` API. [#7855](#7855) * **n-api** * The command-line flag is no longer required to use N-API. [#14902](#14902) * **tls** * Docs-only deprecation of `parseCertString()`. [#14245](#14245) * **New Contributors** * Welcome Sebastiaan Deckers (@sebdeckers) as a new Collaborator! [#15354](#15354)
* **crypto** * Support for multiple ECDH curves. [#15206](#15206) * **dgram** * Added `setMulticastInterface()` API. [#7855](#7855) * **n-api** * The command-line flag is no longer required to use N-API. [#14902](#14902) * **tls** * Docs-only deprecation of `parseCertString()`. [#14245](#14245) * **New Contributors** * Welcome Sebastiaan Deckers (@sebdeckers) as a new Collaborator! [#15354](#15354)
* **crypto** * Support for multiple ECDH curves. [#15206](#15206) * **dgram** * Added `setMulticastInterface()` API. [#7855](#7855) * **n-api** * The command-line flag is no longer required to use N-API. [#14902](#14902) * **tls** * Docs-only deprecation of `parseCertString()`. [#14245](#14245) * **New Contributors** * Welcome Sebastiaan Deckers (@sebdeckers) as a new Collaborator! [#15354](#15354)
* **crypto** * Support for multiple ECDH curves. [#15206](#15206) * **dgram** * Added `setMulticastInterface()` API. [#7855](#7855) * Custom lookup functions are now supported. [#14560](#14560) * **n-api** * The command-line flag is no longer required to use N-API. [#14902](#14902) * **tls** * Docs-only deprecation of `parseCertString()`. [#14245](#14245) * **New Contributors** * Welcome Sebastiaan Deckers (@sebdeckers) as a new Collaborator! [#15354](#15354)
* **crypto** * Support for multiple ECDH curves. [#15206](#15206) * **dgram** * Added `setMulticastInterface()` API. [#7855](#7855) * Custom lookup functions are now supported. [#14560](#14560) * **n-api** * The command-line flag is no longer required to use N-API. [#14902](#14902) * **tls** * Docs-only deprecation of `parseCertString()`. [#14245](#14245) * **New Contributors** * Welcome Sebastiaan Deckers (@sebdeckers) as a new Collaborator! [#15354](#15354)
* **crypto** * Support for multiple ECDH curves. [#15206](#15206) * **dgram** * Added `setMulticastInterface()` API. [#7855](#7855) * Custom lookup functions are now supported. [#14560](#14560) * **n-api** * The command-line flag is no longer required to use N-API. [#14902](#14902) * **tls** * Docs-only deprecation of `parseCertString()`. [#14245](#14245) * **New Contributors** * Welcome Sebastiaan Deckers (@sebdeckers) as a new Collaborator! [#15354](#15354)
* **crypto** * Support for multiple ECDH curves. [#15206](nodejs/node#15206) * **dgram** * Added `setMulticastInterface()` API. [#7855](nodejs/node#7855) * Custom lookup functions are now supported. [#14560](nodejs/node#14560) * **n-api** * The command-line flag is no longer required to use N-API. [#14902](nodejs/node#14902) * **tls** * Docs-only deprecation of `parseCertString()`. [#14245](nodejs/node#14245) * **New Contributors** * Welcome Sebastiaan Deckers (@sebdeckers) as a new Collaborator! [#15354](nodejs/node#15354)
tls.parseCertString()
was made public by mistack. So mark it asdeprecated.
Refs: #14193
Refs: af80e7b#diff-cc32376ce1eaf679ec2298cd483f15c7R188
Checklist
Affected core subsystem(s)
tls, doc