Tech Debt ReportEmissionAllocationService: decouple from the API schema data type
Open
Nobody has claimed this yet.
attn: Devs
BACKLOG
Tech Debt
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Description of the Tech Debt
Tech Debt Triage
The purpose of our technical debt triage process is to analyze technical debt to determine risk level of the technical debt and the value in tackling that technical debt.
Risk Value Scoring:
| Level | Value |
|---|---|
| High | 3 |
| Medium | 2 |
| Low | 1 |
| Technical Debt - Risk Types | Level | Value |
|---|---|---|
| Business Area Risk - Risk of business area visibility / damage to user experience | 0 | 0 |
| Developer Fault Risk - How likely will this tech debt cause a future error related to coding on top of it | 0 | 0 |
| System Fault Risk - Risk of system errors or application downtime | 0 | 0 |
| Time Scale Risk - Compound risk effect if left alone. How much more difficult to fix or dangerous will this become over time? | 0 | 0 |
| Time Sink Risk - How much will this tech debt slow the development process down | 0 | 0 |
| TOTAL SCORE: | 0 | 0 |
Development Checklist:
- Checklist item
- Checklist item
- Checklist item
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
Start by locating ReportEmissionAllocationService and the API schema data type it currently uses. Trace how the service receives and consumes that type, then define the replacement boundary. Done means the service is decoupled from the API schema data type without changing its reported behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100