software-challenge / software-challenge/backend
Color and Team don't get initialised when they should be
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 13
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
With Kotlin, you shouldn't get unchecked NullPointerExceptions or the related IllegalArgumentException. However, sometimes, Colors and Teams aren't initialised even though they should be, resulting in exceptions that shouldn't exist.
https://github.com/CAU-Kiel-Tech-Inf/backend/pull/294/commits/7042b6bc6513c6e9c79b65d92667ecd07766f55c (#294) fails due to this.
Contributor guide
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 inspecting the failing commit 7042b6bc6513c6e9c79b65d92667ecd07766f55c and pull request #294 to identify the path where Color and Team initialization fails. Reproduce the failure and trace the initialization sequence; done means valid initialization prevents the reported NullPointerException and IllegalArgumentException.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100