esamarathon / esamarathon/user-management
Make certain fields editable after the submission period ends
Open
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
A full list of fields is TBD
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points, and says the full list of editable fields is still TBD. Start by clarifying which fields may be edited after submission closes and the expected behavior; the work is not ready to consider done until that scope and its acceptance criteria are defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100