Expose template content in wordpress-state observations#474
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.
Summary
includeContent: truesupport for raw template and template-partcontentinwordpress-statetemplate section artifacts.stylesheetalongsidestylesheetHashonly whenincludeContent: true.runtime-episode-smokecoverage for hashes-only default behavior and include-content template/global-style exports.wordpress.rest-requestcommand so the current main check suite can progress.Closes #444
Checks
npm run buildnpm run runtime-episode-smokenpm run discovery-command-smokegit diff --checknpm run artifact-contract-smokenpm run recipe-site-seed-smokerecipe-interruption-artifacts-smokeBlockers / notes
npm run checkwas attempted twice. The first run hit a transient Playground port collision inartifact-contract-smoke(EADDRINUSE 127.0.0.1:51962), and the isolatedartifact-contract-smokererun passed.recipe-workflow-phases-smoke;recipe-site-seed-smokepassed in isolation afterward.recipe-heavyweight-plugin-runtime-smokefailure atscripts/recipe-heavyweight-plugin-runtime-smoke.ts:91, where the fixture expectedworkflow.activated === "yes"but observedfalse. This PR does not paper over that broader plugin-runtime activation-hook behavior.AI assistance