AccessibleForAll / AccessibleForAll/a11y-advent-calendar
Plan data structure for User
Open
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 27
Description
What data structure do we need for a user? What should be required? What should be optional? Are database and frontend needs the same?
Contributor guide
No contributing guide indexed for this repository
Research direction
Look at existing models or schemas in the repository to understand the current data patterns. Review any API documentation or frontend components that interact with user data. Determine required vs optional fields by considering both database constraints and frontend form validation needs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design, database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100