Elixir / Phoenix LiveView Support
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- elixir
- Domain
- developer-experience
Research direction
Start by reading the Code Connect parser and framework integration entry points to understand how supported frameworks map components to Figma; the issue does not name specific files or tests. The proposed work is an Elixir and Phoenix LiveView integration for .heex templates or LiveView function components, so done means those components can be mapped through Code Connect; the issue provides no implementation guidance or test target.
Written by the indexing model from the issue text.
Description
Support for Elixir and Phoenix LiveView components in Code Connect would be great, so that Figma component definitions can be mapped to .heex templates or LiveView function components.
Phoenix LiveView has gained significant traction for building interactive, server-rendered UIs in Elixir. A Code Connect integration would allow teams using this stack to benefit from the same design-to-code workflow available to React, Vue, and other supported frameworks.
Would love to know if this is on the roadmap, or if there's any guidance on contributing a community-supported parser for Elixir. Happy to help if there's interest!
- 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 ·