-
Notifications
You must be signed in to change notification settings - Fork 0
Add portable metaobject definitions and references to Shopify Toolkit schema dump #25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add portable metaobject definitions and references to Shopify Toolkit schema dump #25
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Adds support for including metaobject definitions and portable metaobject reference validations in the schema dump to enable cross-store portability.
- Introduces dumping of metaobject definitions before metafields.
- Converts metaobject definition GID-based validations to portable type-based validations in both dump and load paths.
- Adds bidirectional conversion logic (GIDs <-> types) and associated tests for one direction.
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| spec/shopify_toolkit/schema_spec.rb | Adds test fixtures and specs for dumping metaobject definitions and converting validations from GIDs to types. |
| lib/shopify_toolkit/schema.rb | Adds metaobject fetching, schema generation with metaobjects, validation conversion, and type detection helpers. |
| lib/shopify_toolkit/metaobject_statements.rb | Adds helper to resolve a metaobject type from a GID for reverse validation conversion. |
| lib/shopify_toolkit/metafield_statements.rb | Adds conversion from metaobject types back to GIDs when creating/updating metafields, plus duplicate type check logic. |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
elia
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think some of the copilot suggestions for extraction could make sense, but feel free to postpone them to the future
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
3eb2ee9 to
5bfb288
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Copilot reviewed 6 out of 6 changed files in this pull request and generated 6 comments.
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
5bfb288 to
3aede8b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Copilot reviewed 6 out of 6 changed files in this pull request and generated 5 comments.
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Copilot reviewed 6 out of 6 changed files in this pull request and generated 10 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
70443b7 to
84f2d9b
Compare
Convert metaobject definition IDs to types in schema dumps to make them
portable across different Shopify stores. Store-specific GIDs are now
replaced with metaobject types that can be resolved in any store.
Changes:
- Add get_metaobject_definition_type_by_gid() method to resolve GIDs to types
- Update schema dump to convert metaobject_definition_id validations to metaobject_definition_type
- Enhance create_metafield and update_metafield to resolve types back to GIDs
- Add precise validation matching for metaobject reference fields only
- Support both single and array values for list.metaobject_reference fields
- Include MetaobjectStatements in Schema module for type resolution
Before:
create_metafield :products, :color, :metaobject_reference,
validations: [{name: "metaobject_definition_id", value: "gid://shopify/MetaobjectDefinition/123"}]
After:
create_metafield :products, :color, :metaobject_reference,
validations: [{name: "metaobject_definition_type", value: "color_pattern"}]
This enables schema files to be shared between different Shopify stores
without manual ID updates, as long as the metaobject types exist.
Add support for dumping metaobject definitions in schema files with portable
cross-store references. Metaobjects are now included before metafields in
the schema dump output.
Changes:
- Add fetch_metaobject_definitions() method to retrieve metaobject schema
- Include create_metaobject_definition calls in schema dump output
- Convert metaobject references within metaobject fields to portable types
- Update schema dump header to mention metaobjects
- Order metaobjects before metafields in dump output
- Handle metaobject field definitions, access controls, and capabilities
- Skip default values (required: false, empty descriptions) for cleaner output
Schema now generates:
create_metaobject_definition :color_pattern,
name: "Color Pattern",
field_definitions: [{key: :name, type: :single_line_text_field, ...}],
access: {admin: true, storefront: false}
create_metafield :products, :color, :metaobject_reference,
validations: [{name: "metaobject_definition_type", value: "color_pattern"}]
This completes the portable schema dump feature by including both
metaobjects and metafields with cross-store compatible references.
Separates the parsing of metaobjects and metafields schema definition
Extracts frequently used methods for handling metaobjects into a shared module.
Updates the metaobject creation logic to correctly handle and process metaobject reference fields
Updates the schema dump functionality to accept and process multiple metaobject_definition_ids
Enhances error handling for metafield creation failures.
Updates schema execution to defer field validation for cross-referencing metaobjects, preventing creation failure when a reference field points to a definition not yet created. The metaobject is created, and the validation update is deferred. Also, access management is updated to skip Admin access settings, as they are not settable via the GraphQL API, preserving only storefront access.
84f2d9b to
7d34277
Compare
elia
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome to see this come along, all the comments can be handled in a different PR later on.
| def execute_metaobject_definitions(schema_content) | ||
| # Create a filtered version that only includes metaobject definitions | ||
| metaobject_content = filter_schema_content(schema_content, :metaobject) | ||
| eval_schema_content(metaobject_content) | ||
| end | ||
|
|
||
| def execute_metafield_definitions(schema_content) | ||
| # Create a filtered version that only includes metafield definitions | ||
| metafield_content = filter_schema_content(schema_content, :metafield) | ||
| eval_schema_content(metafield_content) | ||
| end | ||
|
|
||
| def filter_schema_content(schema_content, type) | ||
| lines = schema_content.lines | ||
| filtered_lines = [] | ||
|
|
||
| # Always include the header and footer | ||
| filtered_lines << lines.first(8) # Header lines up to "ShopifyToolkit::Schema.define do" | ||
| filtered_lines.flatten! | ||
|
|
||
| lines.each do |line| | ||
| case type | ||
| when :metaobject | ||
| if line.strip.start_with?("create_metaobject_definition") | ||
| filtered_lines << line | ||
| end | ||
| when :metafield | ||
| filtered_lines << line if line.strip.start_with?("create_metafield") | ||
| end | ||
| end | ||
|
|
||
| filtered_lines << "end\n" # Closing line | ||
| filtered_lines.join | ||
| end | ||
|
|
||
| def eval_schema_content(content) | ||
| instance_eval(content) | ||
| end |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not to fond of this eval dance, but we can roll with it for now and improve later, my alternative idea would be to enforce the schema definition to declare things in the right order and keep using load here.
In other words if a metaobject definition comes after a metafield definition we throw an error and call it a day. We expect the schema to be generated anyway so it's acceptable to just bail out.
| say_with_time "Executing metafield definitions" do | ||
| # Execute only metafield definitions after all metaobjects exist | ||
| execute_metafield_definitions(schema_content) | ||
| end |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: you don't really "execute" a definition, would sound better as Loading ... definitions
Description
This PR implements support for dumping Shopify Metaobject definitions and references in the schema files, enabling schema portability across different Shopify stores.
Key Enhancements
Metaobject Definitions Dump
fetch_metaobject_definitions()method inschema.rbto retrieve metaobject schemas.create_metaobject_definitioncalls in the schema dump output.Portable References
metaobject_definition_id) to portable metaobject types (metaobject_definition_type) in schema dumps.convert_validations_gids_to_types()method.convert_validations_types_to_gids().list.metaobject_referencefields.Additional Features
MetaobjectUtilitiesmodule to share common methods between modules.Schema Structure Updates
Example Before
Example After
With this update, schema files can be shared between stores without manual ID changes, as long as the relevant metaobject types exist.