-
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
Authentication: Registration #6
Conversation
to me this looks fine so far :) thanks a lot |
I merged #7 and that resulted in conflicts here. Sorry about that. But I just reverted the formatting change - we can merge this and thereafter apply the ocamlformat. :) |
Co-authored-by: Hannes Mehnert <hannes@mehnert.org>
Co-authored-by: Hannes Mehnert <hannes@mehnert.org>
Co-authored-by: Hannes Mehnert <hannes@mehnert.org>
Co-authored-by: Hannes Mehnert <hannes@mehnert.org>
Co-authored-by: Hannes Mehnert <hannes@mehnert.org>
Co-authored-by: Hannes Mehnert <hannes@mehnert.org>
Co-authored-by: Hannes Mehnert <hannes@mehnert.org>
Co-authored-by: Hannes Mehnert <hannes@mehnert.org>
Co-authored-by: Hannes Mehnert <hannes@mehnert.org>
let token = generate_uuid () in | ||
{ token_type = "Bearer"; access_token = Uuidm.to_string token; expires_in } | ||
|
||
let create_user ~name ~email ~password = |
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 guess here a validation should take place, so that name and email are valid. this would then also mean that we don't need the clean_string.
having said this, we can do it in a later PR. :)
Co-authored-by: Hannes Mehnert <hannes@mehnert.org>
Co-authored-by: Hannes Mehnert <hannes@mehnert.org>
Creating users
This PR will focus on authentication. Minor changes are included such as CSS styling.
Frontend:
Endpoints:
/sign-up
/api/register
Backend: