[CLI] Define CLI --flags for each command individually #2930
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.
Motivation for the change, related issues
Running
wp-playground --helppreviously displayed all CLI flags in one long list, making it difficult to tell which flags are relevant to which command. This PR scopes flags to their relevant commands so that runningwp-playground server --helpshows only the flags relevant to theservercommand.Implementation details
Refactors the CLI option declarations from a long chain of
.option()calls to object-based option groups:sharedOptions: Options available to all commands (php, wp, mount, blueprint, etc.)serverOnlyOptions: Options specific to theservercommand (port, multi-worker, devtools)buildSnapshotOnlyOptions: Options specific to thebuild-snapshotcommand (outfile)A
commandWithOptions()helper function applies the appropriate options to each command, combining shared options with command-specific ones.Testing Instructions
Run
wp-playground --helpto see the cleaner top-level help, then runwp-playground server --helporwp-playground build-snapshot --helpto verify command-specific options are displayed correctly.