chandangupta1997 / eventmanagment Goto Github PK

User

1. Register (User can register)
2. Login (User login)
3. Logout (User logout) 04.Change Password (User can change his password)
4. Update Password (When request for reset password is done, to set new password) 06.Reset/Forgot Password (In API response send info regarding to update password) Event (Authentication required for doing operations on event)
5. Create (User can create Event)
6. Invite (Users) // when that user login in he can see his created event list and also events in which he is invited.
7. List (Invited users when login can see their created events as well as events in which they are invited in, also display creator name in list) 04.Following are the actions that need to be done on listing api a. pagination b. Sorting c. Date Filter d. Search Filter
8. Event Detail + list of users invited (API to get specific event and invites) 06.Event update (Event Update)

Agenda ● Understand participants' understanding about the requirement. ● Explain understanding and fill in the gaps in the requirement and the understanding. ● Discuss the roadmap to the solution ● Q & A Roadmap ● Two core models ○ User ○ Event ● Choice of database - mysql/mongodb. Go with mongodb. ● Model schemas - open ended from the client side. Probable schema from our end ○ User ■ Title ● Metadata, - { required, enum [Mr, Miss, Mrs]} ■ name/fullname ■ Email ● Metadata - { required, unique, valid email syntax} ■ Password ● Metadata - { required, use bcrypt } ■ createdAt ■ modifiedAt ■ resetPasswordToken ○ Event ■ name -> title ■ description ■ eventDate ■ createdBy -> userId ■ invitees [{invitee, invitedAt}] ● Data type - array of objects ● Object structure would be { invitee: ObjectId(userId), invitedAt: timestamp } ■ createdAt ■ modifiedAt