Open ashatat opened 6 years ago
I am not sure about the HTML GET /login endpoints
here,
the way I see it they are just routes in the react app?
I mean we should have one endpoint /
that load the react app
then everything will be done inside the react router?
That is true. Too much non-react work got into my head. Will keep it in mind.
I think it's good to have the endpoints here for now, and then we will have an epic react-router issue that will include all of them.
Also whenever we are fetching things from the backend, we will still have to do a get/post/put...etc request.
What do you think?
yeah I think you're right when we write the detailed issues it'll make more sense, I guess
Login:
The login page should include the following components:
Events:
End Point:
/login
Method:
GET
Success response:
200
html
Error response:
500
json
Method:
POST
Validation required: username, passowrd Permission requirement(auth):
none.
Success response:200
json
Sign Up:
The login page should include the following components:
Events:
End Point:
/sign-up
Method:
GET
(will be reassigned to react router later).Success response:
200
html
Error response:
Status Code:
500
Response content type:
json
Response object:
Status Code:
404
Response content type:
json
Response object:
Method:
POST
request object (no OAuth) includes:
Validation required:
Permission requirement(auth):
none.
Success response:status code:
200
Response content type:
json
Redirect:
true
.Response object:
Error response:
Status Code:
500
Response content type:
json
Response object:
Status Code:
404
Response content type:
json
Response object: