Allow mapping nested instances without exposing them as component properties

未关闭
#365 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
typescript

调研方向

Start by reading the Code Connect mapping entry points and how component properties currently resolve nested instances; the issue does not name specific files or tests. Done means a nested instance can map to a code prop without being exposed as a Figma component property. The issue has had no comment for 237 days, so check whether maintainers are still responding before picking it up.

由索引模型根据 Issue 内容生成。

描述

feature request

Problem
Code Connect only lets you map nested components when they are exposed as component properties in Figma. This forces design system teams to expose internal nested instances (e.g. icons inside buttons) even when they should stay private.

Request
Please add support for mapping nested instances in Code Connect without requiring them to be exposed as component properties.

Example
A Button contains a nested Icon, but the icon should not be user‑swappable. Code Connect should still allow mapping that nested icon to a code prop (like endIcon) without exposing it.

主要语言
TypeScript
星标
1.6k
派生
126
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

figma/code-connect 的其他 Issue

查看 figma/code-connect 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。