feat(scaffold): selective example-set removal markers#720
Draft
aryanjasala wants to merge 1 commit into
Draft
Conversation
Mark the demo modules (media-text block extension, theme options, author bio), example components and page-creation pattern with grouped wp:example markers so init can drop selected sets while keeping the rest. The three Main.php modules use keyed markers to scope their shared regions.
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 this does
Marks the theme's demo code so
npm run initcan offer a per-set keep/remove choice on first scaffold.Changes
bin/scaffold.config.js—examples.groups: the three demo modules (media-text block extension, theme options, author bio), the example components (button/card/carousel), and the page-creation pattern.inc/Main.php— the three demo modules share this file, so each scopes its own region with a keyedwp:example:<key>marker; the combineduseis split so each import can be marked individually.How I verified
Ran the init engine's example step for remove-all, remove-subset (e.g.
settings,components), and keep-all: keyed scoping removes only the chosen sets while keeping the rest, markers always stripped,inc/Main.phpand all PHP valid (php -l).Notes
Markers are inert until init processes them — no runtime effect on the built theme. Components and the pattern are delete-only (auto-discovered, nothing to strip).