MaibornWolff / MaibornWolff/codecharta
Adjust behaviour of unavailable metrics
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 529
- Forks
- 56
- Avg merge
- 7h 17m
- Merged PRs (30d)
- 34
Description
# Feature request
When metrics are not available for some files/buildings, they are currently set to zero. While this is fine behaviour, for metrics where higher is better (e.g. coverage) this does not work well. We should adjust this behaviour and allow for distinction between available metrics that are zero and unavailable metrics.
These unavailable metrics would lead to a flat grey building and be highlighted in the metrics view somehow (either a - where the number would be or a new category under secondary metrics thats called unavailable metrics)
## Description
As a user, I want see the difference between metrics that are zero and metrics that are unavailable.
## Acceptance criteria
-
-
-
## Assumptions & Exclusions
## Development notes (optional Task Breakdown)
- [ ]
- [ ]
- [ ]
## Open questions
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing how unavailable metrics become zero and how building colors and the metrics view consume those values. Done means distinguishing unavailable metrics from genuine zero values in both the map and metrics view, with the presentation choice resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- data-visualization, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100