Repository navigation
Keep extension configurations paired across runtime boundaries - #9010
Draft
isaacroldan wants to merge 1 commit into
Draft
isaacroldan wants to merge 1 commit into
isaacroldan wants to merge 1 commit into
Conversation
isaacroldan
force-pushed
the
codex/extension-config-boundaries
branch
from
October 26, 2026 14:43
2373a9d to
c1ca520
Compare
isaacroldan
marked this pull request as ready for review
October 26, 2026 14:44
isaacroldan
force-pushed
the
codex/extension-config-boundaries
branch
from
October 26, 2026 14:56
c1ca520 to
fa1f5d1
Compare
isaacroldan
marked this pull request as draft
October 26, 2026 15:01
This branch has not been deployed
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.
WHY are these changes introduced?
The shared extension model assumes boolean capabilities and loses the relationship between a configuration and its specification. This makes a different capability shape require changes to unrelated consumers or casts at collection boundaries.
WHAT is this pull request doing?
Separate common configuration fields from UI capabilities. Keep each concrete instance paired with its configuration-specific specification, and use runtime interfaces for mixed collections.
Configuration parsing, instance creation, and configuration expansion stay within the owning specification. Construction uses the final merged parser and metadata. UI payload consumers narrow their capability type explicitly.
This is a standalone refactor against
main, which now contains merged #9003. The theme network-access validation and deploy payloads are preserved. Tests that intentionally use partial or invalid configurations have an explicit unvalidated fixture helper rather than weakening production construction.How to manually test your changes?
pnpm shopify app info --path /path/to/appand confirm that the extension list is unchanged.pnpm shopify app build --path /path/to/appand confirm that the extensions build as before.Validation
git diff --checkpassed.Checklist