-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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: cleanup beforeExit for consistency #21113
Closed
Closed
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4075,9 +4075,9 @@ void EmitBeforeExit(Environment* env) { | |
HandleScope handle_scope(env->isolate()); | ||
Context::Scope context_scope(env->context()); | ||
Local<Object> process_object = env->process_object(); | ||
Local<String> exit_code = FIXED_ONE_BYTE_STRING(env->isolate(), "exitCode"); | ||
Local<String> exit_code = env->exit_code_string(); | ||
Local<Value> args[] = { | ||
FIXED_ONE_BYTE_STRING(env->isolate(), "beforeExit"), | ||
env->before_exit_string(), | ||
process_object->Get(exit_code)->ToInteger(env->context()).ToLocalChecked() | ||
}; | ||
MakeCallback(env->isolate(), | ||
|
@@ -4093,8 +4093,8 @@ int EmitExit(Environment* env) { | |
Local<Object> process_object = env->process_object(); | ||
process_object->Set(env->exiting_string(), True(env->isolate())); | ||
|
||
Local<String> exitCode = env->exit_code_string(); | ||
int code = process_object->Get(exitCode)->Int32Value(); | ||
Local<String> exit_code = env->exit_code_string(); | ||
int code = process_object->Get(exit_code)->Int32Value(); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We might as well switch to the non-deprecated versions of |
||
|
||
Local<Value> args[] = { | ||
env->exit_string(), | ||
|
@@ -4106,7 +4106,7 @@ int EmitExit(Environment* env) { | |
{0, 0}).ToLocalChecked(); | ||
|
||
// Reload exit code, it may be changed by `emit('exit')` | ||
return process_object->Get(exitCode)->Int32Value(); | ||
return process_object->Get(exit_code)->Int32Value(); | ||
} | ||
|
||
|
||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
As a pattern, we only store strings on the
Environment
if we expect to use them more than once per isolate, but in the case ofbeforeExit
that’s not the typical case, right?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's not the case for "exit" or "exitCode" either ... so we should either just make them all use
FIXED_ONE_BYTE_STRING
here or put them all inenv
... I'm good either way so long as it's consistent.That said, one could in theory have
beforeExit
happen multiple times ... we've had that happen to us a few times ;-)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.
In that case I’d prefer to follow the pattern and use
FIXED_ONE_BYTE_STRING
for those as well, yeah :)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.
+1... I'll keep
exitCode
onenv
since that is at least used in bothbeforeExit
andexit
. But will makebeforeExit
andexit
each useFIXED_ONE_BYTE_STRING