We’re running into an issue with Code Connect that started last Friday.
We’re currently rebuilding our Design System, and up until last week we were using Code Connect successfully to map Figma components to code in our GitHub repo. Since last Friday, variant restrictions no longer match as expected, so the intended use cases/examples don’t appear even though the file still publishes without errors.
What we observe
-
Publishing the
.figma.tsxfile succeeds. -
Repo access/permissions appear unchanged (Figma still has access to the repo).
-
The Code Connect example that should match a specific variant combination never shows.
-
This exact setup was working correctly before last Friday.
Example:
In our .figma.tsx file for the component (Checkbox), we restrict the example using variant values:
figma.connect( Checkbox, "FIGMA_NODE_URL", { variant: { "Text": "true", "Description Text": "false" }, imports: [ "import { Checkbox } from 'OUR_IMPORT_ROUTE'", "import { Label } from 'OUR_IMPORT_ROUTE'", ], props: { label: figma.string("↳ Label"), }, example: ({ label }) => ( <div className="am-flex am-items-center am-gap-2"> <Checkbox id="checkbox1" /> <Label htmlFor="checkbox1">{label}</Label> </div> ), }, );
The intention is: when the component variant values are Text = true and Description Text = false, Figma should display this example snippet. However, the example never appears, as if the variants are not being matched.
Question
Has anything changed recently in how Code Connect matches variants (Figma properties), or is there a known issue/regression affecting variant restriction mapping?
Happy to provide more details (component screenshot, node structure, variant property names/values, repo structure) if needed.
