This repository has been archived by the owner on May 11, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Implement error handling for all forms #10
Comments
CamiloGarciaLaRotta
changed the title
Setup form input handling
Implement error handling for all forms
Feb 8, 2019
CamiloGarciaLaRotta
added a commit
that referenced
this issue
Feb 16, 2019
- Advances #10 by implementing error handling of the login form - Login is now a reducer component. It performs the authentication and via a callback returns the JWT to the App component. - Services has a side-effect method "authenticate" which POSTs the credentials to the Auth backend. If the login is succesful, it returns the JWT to Login If the login fails, it changes the state of Login to DisplayError - Services has a new type "authResponse" to decode the HTTP response - valueFromEvent was refactored to Services because its used in multiple components Closes #16
CamiloGarciaLaRotta
added a commit
that referenced
this issue
Feb 18, 2019
- Advances #10 by implementing error handling of the login form - Login is now a reducer component. It performs the authentication and via a callback returns the JWT to the App component. - Services has a side-effect method "authenticate" which POSTs the credentials to the Auth backend. If the login is succesful, it returns the JWT to Login If the login fails, it changes the state of Login to DisplayError - Services has a new type "authResponse" to decode the HTTP response - valueFromEvent was refactored to Services because its used in multiple components Closes #16
CamiloGarciaLaRotta
added a commit
that referenced
this issue
Feb 19, 2019
- Advances #10 by implementing error handling of the login form - Login is now a reducer component. It performs the authentication and via a callback returns the JWT to the App component. - Services has a side-effect method "authenticate" which POSTs the credentials to the Auth backend. If the login is succesful, it returns the JWT to Login If the login fails, it changes the state of Login to DisplayError - Services has a new type "authResponse" to decode the HTTP response - valueFromEvent was refactored to Services because its used in multiple components Closes #16
CamiloGarciaLaRotta
added a commit
that referenced
this issue
Feb 20, 2019
- Advances #10 by implementing error handling of the login form - Login is now a reducer component. It performs the authentication and via a callback returns the JWT to the App component. - Services has a side-effect method "authenticate" which POSTs the credentials to the Auth backend. If the login is succesful, it returns the JWT to Login If the login fails, it changes the state of Login to DisplayError - Services has a new type "authResponse" to decode the HTTP response - valueFromEvent was refactored to Services because its used in multiple components Closes #16
handled by 324c3f1 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After all the scrapers are completed, fine-tune the error messages based on the user stories concerning the chrome extension.
e.g. adding a job application without being logged in/being logged in.
The text was updated successfully, but these errors were encountered: