Dia-Dev-Design / Dia-Dev-Design/shearly-next
Modify routes that create or modify users in any way to generate a token
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Modify any already implemented route that modifies the a user (Example: any create or edit route) so that they generate a token and send a response with said token.
The token must contain the following:
- For Clients: email, name, profileImage, phone, address and specialCare.
- For Provider: email, name, profileImage, phone, address, employment, business.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating every implemented route that creates or edits users and identify how each currently sends its response. Ensure client tokens contain email, name, profileImage, phone, address, and specialCare, while provider tokens contain email, name, profileImage, phone, address, employment, and business; done means each applicable route generates and returns the token.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100