Skip to content

[Website] Resolve the Blueprint declaration for the 'View Blueprint' button - #2675

Merged
adamziel merged 1 commit into
trunkfrom
send-blueprint-to-the-editor
Sep 24, 2025
Merged

adamziel merged 1 commit into
trunkfrom
send-blueprint-to-the-editor

Conversation

@adamziel

@adamziel adamziel commented Sep 23, 2025 •

Copy link
Copy Markdown
Collaborator

Motivation for the change, related issues

Improves the #2562 situation in that it brings over the Blueprint to the JSON editor when you click "View Blueprint". It's still not a full solution as the editor doesn't seem to support the "bundled" resources at the moment, e.g.

    {
      "step": "writeFile",
      "path": "/wordpress/wp-content/mu-plugins/rewrite.php",
      "data": {
        "resource": "bundled",
        "path": "./scripts/setup.php"
      }
    },

Still, it improves the user experience so we might land it and keep thinking.

cc @bph @brandonpayton

Testing Instructions (or ideally a Blueprint)

Follow the steps in #2562 and confirm the Blueprint editor shows the correct JSON file.

@adamziel
adamziel merged commit 5e7a197 into trunk Sep 24, 2025
27 checks passed
@adamziel
adamziel deleted the send-blueprint-to-the-editor branch September 24, 2025 16:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant