Plan if Kitchen could be static or not
Open
- Dominant language
- Ruby
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
It is unlikely that new Kitchens will have to be added by users. It would be easier if we don't allow the creation of new kitchens. We would not have to deal with validating uniqness, and other things.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing how Kitchens are created and how uniqueness is validated. The issue proposes deciding whether user-created Kitchens should be disallowed, but names no files, tests, or concrete acceptance criteria. Done would require a settled decision and defined implementation scope.
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