wp-cli: combine two writeFile calles to one writeFiles step.

[bph]

Fixes #104

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• The Plugin and Theme Directories cannot be accessed within Playground.
• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[bph]

Using above test link, Playground ran into theses errors:

[03-Feb-2025 14:59:16 UTC] PHP Fatal: PHP.run() failed with exit code 1 and the following output: �[31;1mError:�[0m Unable to read content from '/wordpress/wp-content/postcontent.md'.
 Error: PHP.run() failed with exit code 1 and the following output: �[31;1mError:�[0m Unable to read content from '/wordpress/wp-content/postcontent.md'.

    at PHP.run (https://playground.wordpress.net/worker-thread-4d378c80.js:53:1888)
    at async PlaygroundWorkerEndpoint.run (https://playground.wordpress.net/worker-thread-4d378c80.js:4:9449)

[03-Feb-2025 14:59:16 UTC] JavaScript Error: PHP.run() failed with exit code 1 and the following output: �[31;1mError:�[0m Unable to read content from '/wordpress/wp-content/postcontent.md'.

Error: PHP.run() failed with exit code 1 and the following output: �[31;1mError:�[0m Unable to read content from '/wordpress/wp-content/postcontent.md'.

    at PHP.run (https://playground.wordpress.net/worker-thread-4d378c80.js:53:1888)
    at async PlaygroundWorkerEndpoint.run (https://playground.wordpress.net/worker-thread-4d378c80.js:4:9449)

[03-Feb-2025 14:59:16 UTC] JavaScript Error: Error when executing the blueprint step #2 ({"step":"wp-cli","command":"wp post create --post_title='Welcome to Playground' --post_status='published' /wordpress/wp-content/postcontent.md"}) : PHP.run() failed with exit code 1 and the following output: �[31;1mError:�[0m Unable to read content from '/wordpress/wp-content/postcontent.md'.

Error: Error when executing the blueprint step #2 ({"step":"wp-cli","command":"wp post create --post_title='Welcome to Playground' --post_status='published' /wordpress/wp-content/postcontent.md"}) : PHP.run() failed with exit code 1 and the following output: �[31;1mError:�[0m Unable to read content from '/wordpress/wp-content/postcontent.md'.

    at Object.run (https://playground.wordpress.net/assets/index-7eeeccac.js:905:146713)
    at async Vu (https://playground.wordpress.net/assets/index-7eeeccac.js:905:148232)
    at async nc (https://playground.wordpress.net/assets/index-7eeeccac.js:905:149113)
    at async https://playground.wordpress.net/assets/main-eaa04db9.js:151:2437

@adamziel any idea what I am missing?

[bph]

returned to writeFile usage.

Tested again and it now works.

[bgrgicak]

Using above test link, Playground ran into theses errors:

@bph this looks like a bug to me. The files are added to the filesystem if I check with await playground.listFiles('/wordpress/wp-content/'), but the CLI command can't find these files.

Could you please open an issue for this?

[bgrgicak]

@bph this looks like a bug to me. The files are added to the filesystem if I check with await playground.listFiles('/wordpress/wp-content/'), but the CLI command can't find these files.

I took another look at this @bph.

Your original Blueprint created a directory with the name postcontent.md and added files named resource and url to the directory.

This behavior matches our implementation of writeFile where a file can only be a literal value or another file tree (represented as a JSON object in the Blueprint).

It would be mindblowing if we could append resource types like URLs in the way you attempted it, so it might be worth submitting a feature request to start a discussion.

[bph]

Thank you @bgrgicak for the sleuthing and encouragement. I added the feature request on the Playground repo
Feature: Add resource type URL to writeFiles step
Please look at it if I captured the issue correctly.