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.
We could keep
--v8-enable-object-printas a valid option in addition to adding--v8-disable-object-printin case anyone is using it, otherwise they'll breakThere 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.
Thanks for your suggestion, I keep the
-v8-enable-object-printflag and add the--v8-disable-object-printflag.If I specify both flags at the same time, We get an exception with a message like
Only one of the --v8-enable-object-print or --v8-disable-object-print options an be specified at a time..Uh oh!
There was an error while loading. Please reload this page.
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.
I believe this introduced a bug? I cannot use "disable" flag because "enable" flag is default True, so if I "disable" then they're both True...
Downloading the source tarball on Nodejs' website for LTS 18.13.0 yields:
Even though the
enableflag is never specified.This is because the
optionsobject has the argparse defaults resolved, which means the enable flag isTrueif not specified... :/