Skip to content

[Blueprints] Resolve Blueprint v2 runtime constants - #3892

Merged
adamziel merged 1 commit into
trunkfrom
resolve-v2-runtime-constants
Jul 3, 2026
Merged

[Blueprints] Resolve Blueprint v2 runtime constants#3892
adamziel merged 1 commit into
trunkfrom
resolve-v2-runtime-constants

Conversation

@adamziel

@adamziel adamziel commented Jul 3, 2026

Copy link
Copy Markdown
Collaborator

What

Carries top-level Blueprint v2 constants into resolveRuntimeConfiguration().

Why

Consumers resolve runtime configuration before booting WordPress. If a Blueprint v2 declaration defines constants, stored-site flows need those constants preserved in the runtime configuration instead of silently defaulting to an empty object.

Testing

  • npm run format:uncommitted
  • npm exec nx run playground-blueprints:test:vite -- --testFiles=packages/playground/blueprints/src/tests/v2/resolve-runtime-configuration.spec.ts
  • npm exec nx run playground-blueprints:typecheck
  • npm exec nx run playground-blueprints:lint
  • git diff --check

Part of #2592.

@adamziel
adamziel force-pushed the resolve-v2-runtime-wordpress-version branch from f8e2d12 to ee84569 Compare July 3, 2026 13:13
@adamziel
adamziel force-pushed the resolve-v2-runtime-constants branch from 2a1136d to 097c970 Compare July 3, 2026 13:14
@adamziel
adamziel force-pushed the resolve-v2-runtime-wordpress-version branch from ee84569 to 8b8a9be Compare July 3, 2026 13:20
Base automatically changed from resolve-v2-runtime-wordpress-version to trunk July 3, 2026 13:20
@adamziel
adamziel requested review from a team and zaerl July 3, 2026 13:20
@adamziel
adamziel force-pushed the resolve-v2-runtime-constants branch from 097c970 to 083e186 Compare July 3, 2026 13:21
@adamziel
adamziel merged commit 0372771 into trunk Jul 3, 2026
48 of 50 checks passed
@adamziel
adamziel deleted the resolve-v2-runtime-constants branch July 3, 2026 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment