Setup › Configuration: hide thresholds behind Advanced so team number and robot file stand out

Abierto
  • ¿Algo no está bien?
#39 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
50/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
frontend

Línea de trabajo

The work is the layout of the Setup › Configuration page in the flashpoint serve UI, which lists the team and connection fields, Robots, about 40 threshold fields from report.toml and anomaly.toml, and the Units table. Start by finding where that page is rendered and how the DEFAULT status shown on the Checks page is detected, since the collapsed Advanced section should depend on it. Done means thresholds sit in a collapsed Advanced section that is closed for bundled defaults, the explanatory line appears, Units shows whether a new team needs it, and no editable field changes.

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

Descripción

enhancement

Found walking through setup on a blank lake and blank config (flashpoint serve on main at 8369dff).

What happens

Setup › Configuration puts everything on one page: Team and connection (3 fields), Robots, then about 40 threshold fields across report.toml and anomaly.toml ([baseline] step_z, [sibling] need, [model] contamination, ...), then the Units table.

For a new team the only real decisions are the team number and a robot file. Everything else has working bundled defaults (Checks shows them as DEFAULT, ok). But the page reads as if you have to understand and fill in all of it, which is scarier than setup actually is.

Expected

  • Team and connection, and Robots, stay at the top as "what you need".
  • Thresholds and anomaly tuning sit behind a collapsed Advanced section, closed by default when the file is the bundled default, with one line: "Defaults work for most teams; change these after a few events."
  • Units stays visible, but says whether a new team needs it on day one.

No change to what can be edited; this is layout only.

Relates to #24.

Lenguaje dominante
Python
Estrellas
0
Forks
1
Merge medio
18 h 37 min
PR fusionados (30 d)
15

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 IgniteRobotics/flashpoint

Todos los issues de IgniteRobotics/flashpoint

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.