Refactor evaluation system
Open
refactor
- Dominant language
- Ruby
- Stars
- 11
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Refactor the evaluation system, so the following changes can be made easily:
- [ ] PointDetails and PointRequests with 0 point, should not be saved
- [ ] Resort leader should be able to edit evaluations
Pundit or cancancan gem could be used for creating polices.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating the evaluation models and the authorization flow for resort leaders, then trace how PointDetails and PointRequests are persisted. Done means zero-point records are not saved and resort leaders can edit evaluations, with coverage for both behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- authorization, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100