-
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
Sign up error handling #256
Conversation
console.log(process.env.REACT_APP_BASE_API_URL); | ||
data: dataToSend, | ||
}) | ||
.then() |
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 need to leave empty then
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.
But should the user somehow be informed that registration is successfull?
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.
It will be used to trigger notification modal #262 as far as I know. That's why I decided to leave it even though it's empty.
part of the #124 task [Sign Up: 400 email exists]
2 first commits are duplicated from #255 PR since they are fixing eslint errors after merge conflicts in #248
after #255 is merged, only 1 file will have changes:
SignUpFormContent
, so please have look only at it[upd: 09/10 now is up to date state]