playground/cli ignores --php, --wp, and --login flags when --blueprint is set

[carstingaxion]

Hello Playground Team,

a call to

@wp-playground/cli/wp-playground.js server --php=7.4 --wp=latest --login

will bring up an instance running on 7.4.31-dev, which is OK.

While a call including a blueprint.json (which does not contain a preferredVersions object) , ...

@wp-playground/cli/wp-playground.js server --php=7.4 --wp=latest --blueprint=./blueprint.json

... will bring up 8.3.0-dev, which is NOT OK.

Is this a known, maybe even wanted or a buggy behavior?

[brandonpayton]

Hi @carstingaxion, this is known behavior and intentional. Though I think it would be good for us to support this use case of "filling in the blanks" or (maybe better) to allow blueprints to explicitly take command-line/query args that are replaced within the Blueprint before it is applied.

[adamziel]

FWIW this is fixed for the Query API in #1731. We should reuse the same argument merging function in CLI.

[bgrgicak]

Let's also allow the --login argument to override Blueprints when we add support for overriding wp and php versions.

[bgrgicak]

I’ve started looking into this and wondered if we could reuse the code from the Website.

While exploring this, I started thinking about the Merging Blueprints issue and the mergeBlueprints function from the Puzzle app.

@adamziel, do you think this would be a good time to work on merging Blueprints, or should I only focus on reusing resolveBlueprintFromURL in the CLI for now?

If we proceed with merging Blueprints, should we build it in PHP to align with Blueprints v2, or treat this as an experiment and use JavaScript?

FYI @brandonpayton, tagging you in case this intersects with your work on Assembler.