Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Topology] Add ghost node during drag to Figma kit

Abierto
#970 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
figma
Área
design, documentation

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Patterns & Extensions Library Topology

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

Design kit scope (suggested)

  • Add Figma representation(s) for the ghost / placeholder node state used during drag (visual treatment aligned with DefaultNode and 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

Lenguaje dominante
Sin datos de lenguaje
Estrellas
50
Forks
40
Sin PR fusionados en 30 d

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de patternfly/patternfly-design-kit

Todos los issues de patternfly/patternfly-design-kit

Issues similares

Más issues de Design

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.