[CLI] Skip interactive mapping phase using the configuration file
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- cli, developer-experience
Research direction
Start by reading the connect command entry point and how it currently reads interactiveSetupFigmaFileUrl from the configuration. Trace the interactive discovery and mapping flow to identify which configuration shape could provide mapping decisions. Done means connect can use mappings from the config and skip the interactive mapping phase; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Description
When using the connect command I'd like to be able to skip the interactive mapping phase and directly provide my mapping decisions from the config file.
Rationale:
Right now the only parameter used by the connect command is interactiveSetupFigmaFileUrl.
However, for the vast majority of my components, I already know which node will be mapped to which file in my repository and asking for the acutal mapping is more of a confirmation than anything else. In the end going through the interactive discovery / mapping phase is not really required.
I know the connect command is not supposed to be run again and again but selecting the components to connect is cumbersome, time-consuming and may lead to configuration errors due to its interactive nature.
- Dominant language
- TypeScript
- Stars
- 1.6k
- Forks
- 126
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from figma/code-connect
-
normalizePropName strips `#` characters from Figma property names instead of only the `#id` suffixOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
figma/code-connect#419 ·
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
figma/code-connect#403 ·
-
feature request
Difficulty 5/5 Over a week Newbie friendliness 38/100
figma/code-connect#414 ·
-
feature request
Difficulty 4/5 3-5 days Newbie friendliness 48/100
figma/code-connect#413 · 1 comment ·
-
feature request
Difficulty 4/5 3-5 days Newbie friendliness 54/100
figma/code-connect#412 · 1 comment ·
All issues in figma/code-connect
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
jeanibarz/knowledge-base-mcp-server#1268 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Koenkk/zigbee-herdsman-converters#13820 ·
Maintainers usually reply within 2 days
-
A live recovery copy treats a large whole number and text with the same digits as the same valueOpenbug sharing & sync
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
[prefer-expect-resolves] autofix leaves a stray ")" when the awaited expression is parenthesizedOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jest-community/eslint-plugin-jest#2052 ·