TBv3: "Verified" chip on repository versions

Abierto
#3,025 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
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript, react
Área
design, frontend

Línea de trabajo

Read repos/RepoHeader.jsx and repos/SourceVersionsTab.jsx and repos/CollectionVersionsTab.jsx, using repos/ProcessingFlag.jsx as the chip pattern. First check the verification API field and the dependency issue #3024; the issue also requires a mockup approval before implementation. Done means the chip appears in both locations, links to the About tab's verification section, has its own icon and tooltip, and its strings are added to all four locale files.

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

Descripción

component/web type/feature

Part of OpenConceptLab/ocl_online#500. Depends on OpenConceptLab/ocl_issues#3024.

A version with a verification summary shows a "Verified" chip that opens the Verification section of its About tab (OpenConceptLab/ocl_issues#1892).

  • Jon approves a mockup first; the new component is flagged as a design-system gap.
  • The chip sits next to the version chip in the repository header and on the version's row in the Versions tab, in ProcessingFlag's pattern (outlined chip with tooltip).
  • Tooltip: "Checked against the publisher's official release". Clicking opens …/<version>/about#verification.
  • Its own icon: VerifiedOutlined already means "released" in the version picker (VersionsTable.jsx:15).
  • Driven only by the API's verification field, never by extras.
  • Strings in all four locale files.

Components: repos/RepoHeader.jsx, repos/ProcessingFlag.jsx (pattern), repos/SourceVersionsTab.jsx, repos/CollectionVersionsTab.jsx.

Lenguaje dominante
Sin datos de lenguaje
Estrellas
4
Forks
2
Merge medio
2 h 12 min
PR fusionados (30 d)
1

Preparar el entorno

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 OpenConceptLab/ocl_issues

Todos los issues de OpenConceptLab/ocl_issues

Issues similares

Más issues de Design

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.