Clarify card/question/model hierarchy
Open
Nobody has claimed this yet.
.Backend
Type:Tech Debt
- Dominant language
- Clojure
- Stars
- 49.3k
- Forks
- 6.8k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 653
Description
* Card is the superclass
* Question and Model are sibling subclasses
* We should reflect this with Toucan models
* We should update variable names as appropriate
* Keeping `/api/card` as it is still makes sense
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 locating the Toucan models and the implementation behind /api/card, then inspect how Card, Question, and Model are currently represented. Done means Card is the superclass, Question and Model are sibling subclasses, variable names reflect that hierarchy, and /api/card remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100