| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Marking this as semver-minor as it documents a feature added in fd644f5. |
Sorry, something went wrong.
There was a problem hiding this comment.
There's not really an authority on this but I think this isn't correct in the way we've been using it.
That is, we italicize what kind of thing we pass to it, not what it actually is. Since that is inconsistent with things that can take multiple values, I left it as just all bold since that is the only way it could ever work anyways.
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
I guess to me the difference is that for NODE_DISABLE_COLORS the "value" is what it actually must be, and for the others it describes what the value should be set to.
I'm not hugely against changing it, but I feel it is no less confusing, perhaps either way.
Sorry, something went wrong.
There was a problem hiding this comment.
Ah I see what you mean. I still think it'be more consistent to still highlight the 1, maybe in the description below as well.
Sorry, something went wrong.
There was a problem hiding this comment.
Leave this out of the --help please. It requires a warning which is far too long and bother some for --help and besides, this option isn't even helpful.
Sorry, something went wrong.
There was a problem hiding this comment.
I feel it has it's place here, even if discouraged. The UNSAFE should make it clear enough that it has a caveat and users can look up details in the man page or in the online docs.
Sorry, something went wrong.
|
@silverwind Could you take a look again? |
Sorry, something went wrong.
There was a problem hiding this comment.
Nit: While you're in here editing the file anyway, can you add a comma after 1? (Makes it clear that the variable should be set to 1 and not 1 colors or something like that.)
Sorry, something went wrong.
|
Fixed nit and highlighted some more values in the man page. Regarding NODE_TTY_UNSAFE_ASYNC in --help, I feel that it should be there for completeness sake. Any other opinions on that one? |
Sorry, something went wrong.
|
I'll make a PR later to remove that env variable, I added it solely at the request of others backwards compat concerns and firmly believe it should not even exist. I have not seen any help requests where people need it either. |
Sorry, something went wrong.
|
Remove. I hope we deprecate it soon then. |
Sorry, something went wrong.
|
Looks like ba4847e introduced two more switches that were only added to the command line help, not to the man page. We should really review those better. |
Sorry, something went wrong.
- add missing environment variables to --help - add missing flags to man page - sort environment variables alphabetically - add some highlighting to the man page - remove stops from descriptions in --help for consistency - few other minor tweaks to --help
|
Fixed merge conflicts and added --trace-events-enabled and --trace-event-categories to the man page. |
Sorry, something went wrong.
|
Going to land this later today unless there are objections. The descriptions for the two new flags were copied as-is from the docs. |
Sorry, something went wrong.
- add missing environment variables to --help - add missing flags to man page - sort environment variables alphabetically - add some highlighting to the man page - remove stops from descriptions in --help for consistency - few other minor tweaks to --help PR-URL: #10157 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Italo A. Casas <me@italoacasas.com> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
|
@silverwind this isn't landing cleanly on v7.x. Mind backporting to v7.x-staging? |
Sorry, something went wrong.
|
@evanlucas it will land clean if you apply ba4847e first, is that good enough? git cherry-pick ba4847e879424ad173289e8fb96cc86a09ee899b
git cherry-pick 2d23562588eebaf9a2a3d3987fe6e4ef63ab9500 |
Sorry, something went wrong.
|
@silverwind unfortunately, I'm pretty sure that commit relies on some changes in v8 that are not in v7.x, so that commit would have to be backported as well. |
Sorry, something went wrong.
- add missing environment variables to --help - add missing flags to man page - sort environment variables alphabetically - add some highlighting to the man page - remove stops from descriptions in --help for consistency - few other minor tweaks to --help PR-URL: nodejs#10157 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Italo A. Casas <me@italoacasas.com> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
- add missing environment variables to --help - add missing flags to man page - sort environment variables alphabetically - add some highlighting to the man page - remove stops from descriptions in --help for consistency - few other minor tweaks to --help PR-URL: #10157 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Italo A. Casas <me@italoacasas.com> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
|
we've opted to not land this on v6.x for now. It can likely land as a patch as the semver minor documentation has already landed on v6.x Please feel free to backport |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
src, doc
Description of change