openboxes / openboxes/openboxes
Refactor reason code enum to be a user-defined table
Open
Nobody has claimed this yet.
status: needs design
type: feature
- Dominant language
- Groovy
- Stars
- 899
- Forks
- 503
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 54
Description
In other words, these should be something an admin can create at runtime and stored in the database.
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
No files, tests, or entry points are named. Start by locating the reason code enum and its database representation, then trace how reason codes are used and administered. Done means an admin can create reason codes at runtime and they are stored in the database.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100