Boot: Move WordPress zip extraction logic to a common unzipWordPress() utility #1427
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.
Moves the WordPress.zip extraction logic to a common utility function called
unzipWordPress
and living in the@wp-playground/wordpress
package. This allows bothremote.html
and Playground CI to boot consistently.This and #1425 unlocks providing WordPress ZIP bundles in Blueprints via
{ "preferredVersion": { "wp": "<URL>" } }
.Implementation details and follow-up work
The goal of
unzipWordPress()
is to extract a zipped WordPress installation at a specified location in VFS. This isn't a trivial task as WordPress might exist at a root of the zip file, at a nested/wordpress
directory, in anotherwordpress.zip
file living inside the initialwp.zip
archive, or in any subdirectory of the above. The current implementation covers a few basic cases, but nothing beyond that.Looking forward, we should:
Testing instructions
Confirm the E2E tests pass