-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
#166240995 User profile creation #19
Conversation
import chaiHttp from 'chai-http'; | ||
import app from '../src'; | ||
|
||
const should = chai.should(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
'should' is assigned a value but never used no-unused-vars
1849b2d
to
855622c
Compare
@deschantkn Fix the Merge conflicts |
@@ -0,0 +1,30 @@ | |||
import models from '../../sequelize/models'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't find any valid reason for creating two files pofiles.js
and users.js
. You can just move all the implementation in the user.js
to ProfileController class to make it more readable.
Anything to say about this suggestion?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No I think this logic is more sound than what I currently have. Will make the necessary changes
855622c
to
429c436
Compare
429c436
to
d698505
Compare
d698505
to
6b94709
Compare
- implement user profile creation - implement user profile fetching functionality - document endpoints - fix token middleware - make request validation middleware reusable [Finishes #166240995]
6b94709
to
a079120
Compare
* feat: add registration validation errors * feat(profiles): implement profiles functionality - implement user profile creation - implement user profile fetching functionality - document endpoints - fix token middleware - make request validation middleware reusable [Finishes #166240995]
* feat: add registration validation errors * feat(profiles): implement profiles functionality - implement user profile creation - implement user profile fetching functionality - document endpoints - fix token middleware - make request validation middleware reusable [Finishes #166240995]
* feat: add registration validation errors * feat(profiles): implement profiles functionality - implement user profile creation - implement user profile fetching functionality - document endpoints - fix token middleware - make request validation middleware reusable [Finishes #166240995]
* feat: add registration validation errors * feat(profiles): implement profiles functionality - implement user profile creation - implement user profile fetching functionality - document endpoints - fix token middleware - make request validation middleware reusable [Finishes #166240995]
What does this PR do?
Enables user to create and update their profile information
Description of Task to be completed?
Implement the following endpoints:
PUT - /api/user
GET - /profiles/:username
How should this be manually tested?
Run the server and use Postman to test
Any background context you want to provide?
N/A
What are the relevant pivotal tracker stories?
#166240995
Screenshots (if appropriate)
N/A
Questions:
N/A