Env: Improve help screen#75783
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Size Change: 0 B Total Size: 6.84 MB ℹ️ View Unchanged
|
|
Flaky tests detected in 64c9744. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/22231019598
|
youknowriad
left a comment
There was a problem hiding this comment.
I like the improvements :)
`yargs` and `chalk` interact poorly, resulting in background colors assigned to the description each command being applied to the white space surrounding each command's description.
`yargs` defaults to `min(80, termWidth)` chars. Try 100 instead. Also, ensure lines are still wrapped to 100 when stdout isn't a terminal (e.g. piping to `less`, writing to file).
And thus remove the unnecessary mention of the `start` command's `--update` option from its description.
The actual port will be revealed upon running `start` anyway.
It remains supported, but yargs will hide it from help screens.
64c9744 to
f6b41f3
Compare
What?
cleanwp-env <command> -- --helpas a general usage formstartandrun:Why?
To scratch an itch.