Description
This is a meta issue to track the efforts of bringing figma-api-stub
to parity with Figma's API. The development will be done in stages for rapid release and merged at @cva-plugin/figma-api-stub before a PR is made here.
NOTE: This is the start of an effort to create a comprehensive Figma Plugin SDK so any help is welcome and we'll try be available and resnposive. More open-source projects (and a roadmap) will be shared latter, for now, just subscribe to this issue to follow updates
EDIT: I've quickly realized that it would be hard to work on this keeping the issues in this repository, so I've recreated them in our fork and linked both the original and the new ones below
This meta issue is at: cva-design#2
Stage 1: Clear open issues and PRs
-
Upgrade to latest @figma/plugin-api via a series of other changes #66
NEW → Upgrade to @figma/plugin-api 1.71 via a series of other changes (Original PR: react-figma#66) cva-design/figma-api-stub#1 -
Styles are missing keys #61
NEW → Styles are missing keys cva-design/figma-api-stub#3 -
Improvements to external styles #46
NEW → Improvements to external styles cva-design/figma-api-stub#4 -
Simulate Error: in set_documentationLinks: Documentation links API takes a list of size 0 or 1 #29
NEW → Implement documentationLinks validation to match Figma API cva-design/figma-api-stub#5 -
getRange... setRange... methods #18
NEW → Text range styling functions cva-design/figma-api-stub#6
Stage 2: Achieving parity
- Generate a report of missing definitions
- Create issues for implementing what's missing
Stage 3: Ensuring parity [TBD]
The goal here is to design an automated process for identifying missing features or breaking changes, automatically creating issues, and, ideally, generating the code and tests automatically