Skip to content

Bundle WordPress HTML API in Symfony Blueprint#207

Merged
adamziel merged 2 commits into
trunkfrom
add-symfony-html-api-composer
Jun 8, 2026
Merged

Bundle WordPress HTML API in Symfony Blueprint#207
adamziel merged 2 commits into
trunkfrom
add-symfony-html-api-composer

Conversation

@adamziel

@adamziel adamziel commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

What it does

Updates the Symfony Playground Blueprint ZIP so the bundled Symfony app includes a Composer-installed playground/wordpress-html-api package.

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 uses preferredVersions.wp: false.

Why

The Playground docs Symfony example should parse the rendered <h1> with WP_HTML_Processor instead of preg_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-blueprints

Also verified locally that the bundled app autoloader exposes WP_HTML_Processor and that the Symfony route still renders.

@adamziel adamziel merged commit 7004a19 into trunk Jun 8, 2026
2 checks passed
@adamziel adamziel deleted the add-symfony-html-api-composer branch June 8, 2026 10:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant