Theme Developers Get Pre-Upload Validation Checks
Theme builders now catch unsupported field types, bad assets, deprecated tags, over-nested schemas, and duplicate field names before upload, so broken themes never reach a live site.
Theme developers can now catch the most common theme problems before a theme is ever uploaded. Validation runs while you build, surfacing issues during development instead of after a theme goes live. The result is fewer broken sites and far less time spent tracing a problem back to a malformed schema or a missing file.
What it catches
Validation now flags the issues that most often break a theme. It catches unsupported field types in block and template schemas, asset files that use a disallowed format, and assets that ship in a theme but are never referenced by any template. It also flags duplicate field names within a schema, which could otherwise lead to confusing editing forms.
Cleaner, more maintainable themes
Two checks help keep themes healthy over time. Deprecated include tags are flagged with a recommendation to use the current equivalent, so older patterns get retired instead of quietly lingering. Deeply nested schemas are reported as well, since over-nested groups and arrays make editing forms harder to use and harder to maintain.
Why it matters
Surfacing these problems before upload means a theme that passes validation is far more likely to render correctly on a real site. Problems are caught by the developer, during development, rather than by an editor staring at a broken page.