[Topology] Add ghost node during drag to Figma kit
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- figma
- 领域
- design, documentation
调研方向
Start with the merged react-topology PR #311 and its design-review asset, then inspect the existing topology components and tokens in the Figma kit, especially DefaultNode and DefaultEdge. Add the ghost-node state, document when it appears during drag, and check whether freezeEdgeDuringNodeDrag needs an example update. Done means the visuals, usage notes, token alignment, and relevant release cross-link are present.
由索引模型根据 Issue 内容生成。
描述
Summary
@patternfly/react-topology now supports an optional ghost node (non-interactive placeholder) at a node's original position while the real node is being dragged, so edges do not appear to hang in empty space. This work should be reflected in the PatternFly design kit (Figma) so designers can spec and review the interaction consistently with implementation.
Upstream references
-
Feature request: patternfly/react-topology#305 — Nodes - Add optional ghost node at original position during drag operations
-
Implementation (merged): patternfly/react-topology#311 — feat: show ghost node during node drag (includes design-review asset in the PR description)
-
Shipped on prerelease: comment on #305 — 6.5.0-prerelease.5
Design kit scope (suggested)
-
Add Figma representation(s) for the ghost / placeholder node state used during drag (visual treatment aligned with
DefaultNodeand existing topology tokens). -
Document when the ghost appears vs. the live dragged node (interaction note or kit annotation), matching the optional API behavior in code.
-
If applicable, update topology examples or pattern frames so drag scenarios show the ghost for handoff and QA.
Acceptance criteria
-
Ghost-node visuals and usage are documented in the kit in line with the merged react-topology behavior.
-
Any new styles use existing design tokens / library styles where possible.
-
Cross-link or changelog note pointing designers to the react-topology release when this lands in a stable channel (if kit ships before/after stable).
Notes
Upstream also notes a related change in DefaultEdge around freezeEdgeDuringNodeDrag (see PR #311). Confirm whether kit edge documentation or examples need a small alignment pass.
Jira Issue: PF-3924
- 主要语言
- 没有语言数据
- 星标
- 50
- 派生
- 40
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
patternfly/patternfly-design-kit 的其他 Issue
-
PatternFly 6
难度 5/5 一周以上 新手友好度 25/100
-
难度 2/5 1-3 小时 新手友好度 35/100
-
React component groups
难度 5/5 一周以上 新手友好度 25/100
-
PatternFly 6
难度 4/5 3-5 天 新手友好度 35/100
-
Component Library
难度 2/5 1-3 小时 新手友好度 48/100
查看 patternfly/patternfly-design-kit 的全部 Issue
相似的 Issue
-
area/busola/ux
难度 2/5 1-3 小时 新手友好度 75/100
kyma-project/busola#5344 ·
-
bug
难度 2/5 1-3 小时 新手友好度 75/100
-
deck: add to staging enhancement feature: UI Cleanup & Documentation level: easy priority: MUST HAVE ready for dev lead role: DevOps size: 1pt
难度 2/5 1-3 小时 新手友好度 75/100
hackforla/tdm-calculator#3547 ·
-
难度 2/5 1-3 小时 新手友好度 75/100
-
bug
难度 2/5 1-3 小时 新手友好度 75/100
SAP/fundamental-ngx#14560 ·