-
Notifications
You must be signed in to change notification settings - Fork 29.1k
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: experimental flag for global accessible APIs #54330
doc: experimental flag for global accessible APIs #54330
Conversation
50dca30
to
b83e9b3
Compare
Updated per nodejs/TSC#1608. |
@nodejs/tsc please take a look, thanks :) |
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.
It might be good to add an explainer on why adding a global is considered semver-major
(IIRC it's in case user code is using if(typeof newGlobalVar === 'undefined') /* Node.js specific code here */
). IMO we should also better define what we mean by "the global scope", because I think you mean more than just the global object, but anything that's available without an import/require, right?
b83e9b3
to
deb442d
Compare
Explicitly document that adding an API to the global scope requires `semver-major` label. Waiving the `semver-major` requires a regular TSC consensus process.
deb442d
to
03b7ace
Compare
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
Thanks for suggestion, updated! |
Adding
tsc-agenda
|
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
Landed in 23f8ed0 |
Explicitly document that adding an API to the global scope requires `semver-major` label. Waiving the `semver-major` requires a regular TSC consensus process. PR-URL: #54330 Refs: #54329 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Michael Dawson <[email protected]>
Explicitly document that adding an API to the global scope requires
semver-major
label. Waiving thesemver-major
requires a regularTSC consensus process.
Refs: #54329