popcodeorg / popcodeorg/popcode

React key warning in development mode

Abierto
#1,226 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

bug
Lenguaje dominante
JavaScript
Estrellas
191
Forks
143
Merge medio
4 d 11 h
PR fusionados (30 d)
5

Descripción

When developing, if you open a fresh Popcode environment and type <h1 into the HTML editor, the console displays this React warning:

Warning: Encountered two children with the same key, `unclosed-tag,8`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version.
    in ul (created by ErrorList)
    in div (created by ErrorList)
    in ErrorList (created by ErrorReport)
    in div (created by ErrorReport)
    in ErrorReport (created by Connect(ErrorReport))
    in Connect(ErrorReport) (created by Output)
    in div (created by Output)
    in div (created by Output)
    in Output (created by Workspace)
    in div (created by Workspace)
    in div (created by Workspace)
    in main (created by Workspace)
    in div (created by Workspace)
    in Workspace (created by Connect(Workspace))
    in Connect(Workspace) (created by Application)
    in Provider (created by Application)
    in Application

You don't see this in production since the warnings get stripped in the production version of React. Just wanted to note this—feel free to close if you already know about it or aren't worried about it.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

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.

Línea de trabajo

Reproduce la advertencia abriendo un entorno de Popcode nuevo y escribiendo <h1 en el editor HTML. Empieza por el componente ErrorList mencionado en el stack trace de React e inspecciona cómo reciben sus claves los elementos de la lista; se considera terminado cuando la advertencia de claves duplicadas ya no aparece en desarrollo.

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

Evaluación

Stack tecnológico
javascript, react
Área
frontend
Tipo de issue
Error
Dificultad
2/5
Tiempo estimado
1-3 horas
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.