feat: drill into an application's resources

Abierto
  • ¿Algo no está bien?
#167 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
aws, rust
Área
cli, cloud

Línea de trabajo

The issue points to src/app/mod.rs for the FindingRoute jump and src/ui/keys.rs for key registration; read docs/recipes/README.md first and check the dependency on #165. Build and test the resource list, then verify that Enter opens it, resource selection jumps to the service view, Esc returns, and the footer and help show the keys. The issue says unit tests are enough; README and a changeset are also required.

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

Descripción

size: M

Why

The last slice of #90: press Enter on an application to see every resource behind it.

Steps

  1. Enter on an Application row opens a list of that application's resources: service, name, region, and Component tag.
  2. Enter on a resource row jumps to that service's view with the row selected. Look at how FindingRoute is used to jump from Findings.
  3. Esc returns to the Application list.
  4. Add the keys to the key registry so the footer and help stay correct (see #69).

Where to look

  • src/app/mod.rs (FindingRoute jump)
  • src/ui/keys.rs
  • #69

Done when

  • Drill-down and jump work
  • Footer and help show the keys
  • Tests for the resource list builder
  • README, changeset
  • cargo fmt --all, cargo clippy --all-targets -- -D warnings, and cargo test --all pass, with output pasted in the PR

Check against AWS

Optional. Unit tests are enough for this issue.

Out of scope

Editing tags from Glance. Glance is read-only.

Blocked by

#165. Start this after that is merged.

Size: M. Read docs/recipes/README.md before starting.

Lenguaje dominante
Rust
Estrellas
2
Forks
0
Merge medio
4 h 8 min
PR fusionados (30 d)
8

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 fells-code/seamless-glance

Todos los issues de fells-code/seamless-glance

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.