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
{{ message }}
This repository was archived by the owner on Apr 9, 2026. It is now read-only.
As a specs user, many types come out of the box, like container, text, and slot. But what if I want a custom primitive type like a mark or other type of asset? I don't know how to define those or extend the schema model to support them.
Precedent
The anova schema has moved past just Figma native types (including VECTOR, LINE, etc) to include "custom" types in the form of ICON. This custom type requires processing rules to detect it as an element, note it as a specialized anatomy type, and process certain styles and/or configurations per element and variant. The impact is large across many schema / transformer areas. But it could be modularized.
Problem
As a specs user, many types come out of the box, like container, text, and slot. But what if I want a custom primitive type like a mark or other type of asset? I don't know how to define those or extend the schema model to support them.
Precedent
The anova schema has moved past just Figma native types (including
VECTOR,LINE, etc) to include "custom" types in the form ofICON. This custom type requires processing rules to detect it as an element, note it as a specialized anatomy type, and process certain styles and/or configurations per element and variant. The impact is large across many schema / transformer areas. But it could be modularized.