-
Notifications
You must be signed in to change notification settings - Fork 30k
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
src: deprecate vm.runInDebugContext #12815
Conversation
Will there be no similar behavior? |
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.
The deprecation status in doc/api/deprecations.md also needs to be changed to Runtime.
@@ -311,6 +311,11 @@ console.log(util.inspect(sandbox)); | |||
## vm.runInDebugContext(code) | |||
<!-- YAML | |||
added: v0.11.14 | |||
deprecated: v8.0.0 |
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.
This change should go in separately with v8.x.
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.
This should be REPLACEME
rather than listing a specific version here.
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.
@TimothyGu Done (but deprecated: v8.0.0
is correct since that’s when we docs-deprecated)
'a future version.'; | ||
common.expectWarning('DeprecationWarning', msg); | ||
/* eslint-disable no-unused-vars */ | ||
const _ = vm.runInDebugContext(); |
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.
Why const _
?
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.
@TimothyGu done
ping @joshgav |
@fhinkel Yes I believe so. |
Should we reopen since #13295 won't be in v9? |
@targos yup |
1894455
to
66fa03d
Compare
I don’t think @joshgav is very active right now, so I’ve rebased and force-pushed this. @nodejs/tsc This needs to be in Node 9, ptal CI: https://ci.nodejs.org/job/node-test-commit/13371/ (edit: self-assignment to keep track, shouldn’t stop anybody from merging) |
I just pushed a commit to change the deprecation type in the documentation. |
Landed in 88e55fe |
PR-URL: #12815 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
PR-URL: nodejs/node#12815 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
PR-URL: nodejs/node#12815 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
Runtime deprecation of
vm.runInDebugContext
. To land in v9.x.