Skip to content
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

feat: complete registration screen #151

Merged
merged 5 commits into from
Nov 6, 2023
Merged

feat: complete registration screen #151

merged 5 commits into from
Nov 6, 2023

Conversation

cka-y
Copy link
Contributor

@cka-y cka-y commented Nov 2, 2023

Summary:

Closes #148

This PR is only covering the UI components related to the registration process. The logic will need to be implemented as tested as part of the upcoming issues.

Tasks left to completion to ensure proper behaviour of user registration:

Expected behavior:

Screenshot 2023-11-02 at 2 30 25 PM

Please make sure these boxes are checked before submitting your pull request - thanks!

  • Run the unit tests with ./scripts/api-tests.sh to make sure you didn't break anything
  • Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
  • Linked all relevant issues
  • Include screenshot(s) showing how this pull request works and fixes the issue(s)

Copy link

github-actions bot commented Nov 2, 2023

Preview Firebase Hosting URL: https://mobility-feeds-dev--pr-151-cvxsi2cq.web.app

Comment on lines 50 to 53
await updateProfile(user, {
displayName: values?.fullname,
});
dispatch(refreshUserInformation(user));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This operation should be abstracted from the component. The update of the profile should be in the saga layer not the component.

web-app/src/app/router/Router.tsx Outdated Show resolved Hide resolved
});
dispatch(refreshUserInformation(user));

navigateTo(ACCOUNT_TARGET);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The navigation should be done after the network call is succeeded. We need to add error handling in case a network call fails.

Copy link
Member

@davidgamez davidgamez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@davidgamez davidgamez merged commit ea9a341 into main Nov 6, 2023
4 checks passed
@davidgamez davidgamez deleted the feat/113 branch November 6, 2023 19:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Web UI: Collecting contact information after API registration
2 participants