You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upload settings_schema.json before validator-consumer assets
The CLI uploaded `config/settings_schema.json` and `config/settings_data.json` together as the LAST batch of theme files. Server-side validators on blocks, sections, section-group JSON, and template JSON resolve dynamic-source defaults of the form `{{ settings.<theme_setting>.* }}` against the theme's currently-stored schema. On the first push to a fresh dev theme that schema is empty, so any asset whose schema references a not-yet-declared theme setting fails validation — the user sees errors like "Invalid schema: setting with id=... default must be a color or dynamic source access path" or "Dynamic source default value added to '...' is invalid". A second push then succeeds because the user's real schema is now on the server.
Split the `configFiles` partition bucket into `configSchemaFile` and `configDataFile` and reorder the dependent upload chain so schema lands first and data lands last. Schema has no upstream dependencies; data legitimately needs to be last because its current and presets validate against the freshly-uploaded schema. The matching delete order is inverted accordingly.
Closesshop/issues-merchant-workflows#1929
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Upload `config/settings_schema.json` before block, section, section-group, and template assets so dynamic-source defaults referencing newly declared theme-level settings validate correctly on the first push to a fresh dev theme.
0 commit comments