Tracking issue for Clearing Issues and PRs #2
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.
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 replicate at react-figma#67
Stage 1: Clear open issues and PRs
- Upgrade to @figma/plugin-api 1.71 via a series of other changes (Original PR: react-figma#66) #1
original: Upgrade to latest @figma/plugin-api via a series of other changes react-figma/figma-api-stub#66 - Styles are missing keys #3
original: Styles are missing keys react-figma/figma-api-stub#61 - Improvements to external styles #4
original: Improvements to external styles react-figma/figma-api-stub#46 - Implement documentationLinks validation to match Figma API #5
original: Simulate Error: in set_documentationLinks: Documentation links API takes a list of size 0 or 1 react-figma/figma-api-stub#29 - Text range styling functions #6
original: getRange... setRange... methods react-figma/figma-api-stub#18
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