[FEATURE] Setup User Model
- Dominant language
- PHP
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
Currently the user only contains a name, email and password fields, we might want to store more (or less) data of the user.
**Describe the solution you'd like**
Think about what fields we need for the user (non-relational) such as first name, last name, address, etc...
If it's not needed, I'd recommend to not store that data.
Also if it's anything sensitive, we should look at a way to encrypt that data and keep that data secure.
**Describe alternatives you've considered**
n.t.b
**Additional context**
n.t.b
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by locating the existing User model and documenting its current fields, then clarify which non-relational fields are required and which sensitive values need protection. The work is done when the user schema and secure handling requirements are agreed and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100