cleodora-forecasting / cleodora-forecasting/cleodora
cleosrv: Use a DB transaction in the createForecast mutation resolver
Open
- Dominant language
- Go
- Stars
- 24
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Same as the resolveForecast() mutation resolver.
Contributor guide
Research direction
Start at the cleosrv createForecast mutation resolver and compare it with resolveForecast(), which is the only implementation reference in the issue. Trace the existing database transaction handling and verify that createForecast has the same behavior; the issue provides no test or file path, so completion must be confirmed from the resolver's transaction semantics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, graphql
- Domain
- api, backend, database
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100