MaibornWolff / MaibornWolff/codecharta
Change how parser prefixes are handled
- Dominant language
- TypeScript
- Stars
- 529
- Forks
- 56
- Avg merge
- 7h 17m
- Merged PRs (30d)
- 34
Description
# Feature request
Currently metrics generated by the parser get a prefix of that parsers name (e.g. sonar_coverage). This would split that prefix off of the metric name and show it somewhere else in the metrics card. Here are some mockups of how that could look:

## Description
As a user, I want to have the metric and the parsers name separated so that i can primarily focus on the metric but still have the information of where it came from available.
## Acceptance criteria
-
-
-
## Assumptions & Exclusions
- If a metric is calculated by multiple parsers and they result in different values, they are treated as different metrics, differentiated by the parser they are from
- If a metric is calculated by multiple parsers and they result in the same value, they are treated as one metric but multiple parsers are shown for their 'origin'
## Development notes (optional Task Breakdown)
- [ ]
- [ ]
- [ ]
## Open questions
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by tracing parser-generated metric names into the metrics card, then clarify the missing acceptance criteria for separating metric names from parser origins and handling equal or conflicting values; done should satisfy those clarified cases and match the supplied mockups.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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