feat: show finding counts per application

Open Beginner friendly
  • Is something wrong?
#164 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
backend, cli

Research direction

Read docs/recipes/README.md, then inspect src/app/applications.rs and src/models/finding.rs to understand how application resources and findings are grouped. Issue #163 must be merged first. Add the High and Medium count columns, exclude findings without a resource ID, explain that exclusion in the view, and test the resource-to-application mapping; done means the checks listed in the issue pass and a changeset is included.

Written by the indexing model from the issue text.

Description

size: S

Why

"Is product X healthy" is the main question the Application view answers. Findings already carry a resource_id, so they can be mapped back to the resource's tags.

Steps

  1. Build a map from resource ID to application value while grouping.
  2. Add High and Medium finding counts as columns.
  3. Findings with no resource ID are not counted. Say so in the view footer or help text.
  4. Tests for the mapping.

Where to look

  • src/app/applications.rs
  • src/models/finding.rs

Done when

  • Columns show counts
  • Tests
  • 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.

Blocked by

#163. Start this after that is merged.

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

Dominant language
Rust
Stars
2
Forks
0
Avg merge
4h 8m
Merged PRs (30d)
8

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fells-code/seamless-glance

All issues in fells-code/seamless-glance

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.