figmagic icon indicating copy to clipboard operation
figmagic copied to clipboard

Figmagic is the missing piece between DevOps and design: Generate design tokens, export graphics, and extract design token-driven React components from your Figma documents.

Results 12 figmagic issues
Sort by recently updated
recently updated
newest added

**Describe the bug** Hi, since you added support for frame variants, it's not ignoring prefixed frames with the '_' or ':' prefixes **Expected behavior** These shouldn't be added to the...

wontfix
user-error

Currently, when generating elements (i.e. "React components"), images are not supported. Example: If you were to generate a button with a background-image, the generation would attempt to understand the general...

enhancement

**Describe the bug** There's difference in the gradient that Figma outputs and the one that figmagic returns. Both in the `angle` of the gradient, and in the `color stops`. You...

bug
help wanted

This issue results in tests relating to named versions (such as `4.1.0`) to fail after those 30 days have passed. See if this can be mocked. There is a separate...

tests

Currently, colors do not support blend modes. This issue would adress adding support for blend modes. I currently have no clear idea of how this would manifest itself; perhaps it...

enhancement

The test `"It should write graphic elements and check that graphic elements map file exists"` for `createElements()` is flaky and fails in CI, but seemingly not on a local machine....

ci
technical-debt

Support "compositions" that are higher-order components (groups?) referring to nested elements. This would enable creating for example a Form that would contain elements (Button, Heading, Paragraph). Currently, this needs to...

enhancement

A small number of tests seem to fail exclusively on Windows CI builds: - `getFileContentAndPath.test.ts` - `prepFile.test.ts` - `getSvgFileData.test.ts` This might have to do with CRLF or some similar "invisible"...

ci
technical-debt

(This is an older, anecdotal issue and needs to be re-verified and investigated!) It is not possible to group elements inside each other, making (React) element generation less powerful (i.e....

bug

(This is an older, anecdotal issue and needs to be re-verified and investigated!) This concerns (React) element generation. Non-nested elements need to have the layout element using the Component name...

bug