Replace strong database relations with weak ones
Open
- Dominant language
- Kotlin
- Stars
- 25
- Forks
- 6
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 9
Description
AC:
- TokenProperty should not have user and token, but userId and tokenId
- Check Riddles for similar
- Check Task for similar
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the TokenProperty, Riddles, and Task definitions, then compare how their user and token relations are declared. Use the acceptance criteria to identify the corresponding ID fields and check each named entity for similar relations; the work is done when all listed relations match the requested weak form and the project still builds and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, spring-boot
- Domain
- backend, database
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100