-
Notifications
You must be signed in to change notification settings - Fork 0
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
FE New User Flow #36
FE New User Flow #36
Conversation
pcatkins
commented
Jan 17, 2024
- New unit test for partial user create success
- Route protection for /new-user routes
- Get user and create user API calls
- Check for existing user, show dashboard or new-user page accordingly
src/ECER.Clients.RegistryPortal/ECER.Clients.RegistryPortal.Server/Users/UserInfoEndpoints.cs
Show resolved
Hide resolved
|
||
// Check if the response has data and userInfo property | ||
return response?.data?.userInfo ?? null; | ||
} catch (error) { |
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.
should it be more specific catch on 404?
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.
Yes can do. It doesn't change much as far as handling the error at this point. We still need to identify how we want to handle errors FE moving forward (alert/toast user, log?, etc.).
Adjusted to add catch 404
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.
not exactly - 404 here has a true meaning: that user was not found, hence it is a new user