Role of Component name
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- kotlin, typescript
- Domain
- developer-experience, documentation
Research direction
Start with the Compose Code Connect documentation linked in the issue and trace how the Composable function name is used in suggested imports and as the Figma component name. The issue asks for the suggested import to resolve correctly and for the component name's role to be explained; confirm the relevant documentation and suggestion behavior before deciding what change is needed.
Written by the indexing model from the issue text.
Description
I realised that the name of the function annotated with @Composable is used in two places :
- in the import inside suggest code (see screenshot)
- as the component name (I'm not sure what the component name is used for anyway in Compose)
The import in the suggested code should be fixed, and point to the real import
The role of the component name in Figma should be better explained in https://developers.figma.com/docs/code-connect/compose/
Please provide:
- Code Connect CLI version 1.3.13
- Operating system MacOS 26.2
- Code Connect file
@file:Suppress("unused")
package com.mycomapny.designsystem
import androidx.compose.runtime.Composable
import com.figma.code.connect.FigmaConnect
import com.figma.code.connect.FigmaVariant
import com.navico.argonsdk.compose.slider.Slider
@FigmaConnect(url = "https://www.figma.com/design/4Lp9RNH2jS1KmFqwFNJlXZ/TestFile?node-id=1-35&t=gFRxObRkPosXZapP-4")
@FigmaVariant("Style", "Horizontal")
private class TestFigma {
@Composable
fun Slider1() {
Slider.Horizontal(
value = 1f,
onValueChange = {},
)
}
}
@FigmaConnect(url = "https://www.figma.com/design/4Lp9RNH2jS1KmFqwFNJlXZ/TestFile?node-id=1-35&t=gFRxObRkPosXZapP-4")
@FigmaVariant("Style", "Vertical")
private class TestVerticalFigma {
@Composable
fun Slider2() {
Slider.Horizontal(
value = 1f,
onValueChange = {},
)
}
}
- 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 ·