-
Notifications
You must be signed in to change notification settings - Fork 3
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
#164798256 Enable users manipulate articles #15
#164798256 Enable users manipulate articles #15
Conversation
@@ -0,0 +1,25 @@ | |||
.article-title { | |||
font-size: 40px; |
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.
Properties should be ordered color, font-size, text-align
.btn-primary { | ||
color: #fff; | ||
background-color: #003153; | ||
border-color: #003153; |
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.
Color literals like #003153
should only be used in variable declarations; they should be referred to via variable everywhere else.
} | ||
.btn-primary { | ||
color: #fff; | ||
background-color: #003153; |
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.
Color literals like #003153
should only be used in variable declarations; they should be referred to via variable everywhere else.
4a35042
to
11f7e97
Compare
11f7e97
to
5d2603e
Compare
5d2603e
to
c891391
Compare
c891391
to
7e88fcb
Compare
7e88fcb
to
8bd7cfb
Compare
8bd7cfb
to
0b4bf56
Compare
0b4bf56
to
569f4a7
Compare
569f4a7
to
9f31611
Compare
f8bd879
to
77dc529
Compare
77dc529
to
d55b4fc
Compare
23c726f
to
50ac036
Compare
50ac036
to
5b5e43f
Compare
5b5e43f
to
dee5d73
Compare
dee5d73
to
a4edaae
Compare
a4edaae
to
17726c8
Compare
17726c8
to
eb00933
Compare
} | ||
onSubmit(e) { | ||
e.preventDefault(); | ||
const messageObject = { |
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.
@patrickf949 you could do well with destructuring this.
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.
good work with destructuring
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.
Thanks @e-ian
@@ -23,7 +23,10 @@ export const userLoginRequest = userData => async dispatch => { | |||
|
|||
sessionStorage.setItem("token", response.data.user.token); | |||
sessionStorage.setItem("username", response.data.user.username); | |||
sessionStorage.setItem("email", response.data.user.email); |
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.
@patrickf949 why are we storing the email in session here.
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.
@e-ian, the email is the most unique way of identifying a user, and that's what we are basing on in the backend to filter user articles
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.
Okay but the username
is equally unique in our backend.
eb00933
to
213ee2d
Compare
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.
GREAT WORK @patrickf949
213ee2d
to
c04ee4c
Compare
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.
LGTM
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.
Great work @patrickf949 .
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.
Great implementation of the articles creation and retrieval. However, the retrieval of articles for a specific user is not working if one is logged in using social auth. This could be because the email is not saved in session storage on social login success. You may need to add it in the social auth action.
c04ee4c
to
e8b8274
Compare
- add routes for article creation and viewing - add necessary pages for article creation and viewing - write tests for all functionality [Finishes #164798256]
e8b8274
to
f0dd23d
Compare
Thanks @MuhanguziDavid all done |
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.
LGTM
What does this PR do?
Enables users to create and read articles
Description of Task to be completed?
How should this be manually tested?
Setup the application as stated here
Create and verify a user - here
Create articles with the following routes
localhost:8000/create-article
--Simulated hereView articles on the landing page and click on them to get the full article --Simulated here
What are the relevant pivotal tracker stories?
164798256
Screenshots
Create an article
View all articles