Any plan on storing Tod::Shift as ActiveRecord attribute?
Open
- Dominant language
- Ruby
- Stars
- 447
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
Just asking. It would be a perfect fit for open business schedules.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue only asks whether Tod::Shift should be stored as an ActiveRecord attribute and names no files, tests, or entry points. Start by clarifying the intended ActiveRecord behavior and acceptance criteria; the work is done when an agreed design and implementation path are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100