Bundle WordPress HTML API in Symfony Blueprint#207
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What it does
Updates the Symfony Playground Blueprint ZIP so the bundled Symfony app includes a Composer-installed
playground/wordpress-html-apipackage.That package contains the WordPress HTML API runtime files needed for
WP_HTML_Processor, but it does not install or boot WordPress. The Blueprint still usespreferredVersions.wp: false.Why
The Playground docs Symfony example should parse the rendered
<h1>withWP_HTML_Processorinstead ofpreg_match(). Bundling the HTML API through Composer keeps the docs example realistic while preserving the point of the demo: Symfony can run in Playground without downloading WordPress.Testing
CHANGED_FILES=$'blueprints/symfony-package-radar/symfony-package-radar.zip' \ GITHUB_BRANCH=add-symfony-html-api-composer \ npm run validate:pr-blueprintsAlso verified locally that the bundled app autoloader exposes
WP_HTML_Processorand that the Symfony route still renders.