Updating UI and behavior after registering

[jtkabenni]

Description

Updates to behavior and UI after user registration:

• redirected to home page after account created
• Welcome message modal appears after user authenticates for the first time (creating account)
• Modal does not appear again after it is closed out
• user context created so logged in user information is global
• firebase API functions for user added to new api file
• new field closedConfirmationMessage added to DB to track whether user has closed message or not

Related Issue

https://cherryontech-jupiter-jumpers.atlassian.net/browse/SCRUM-12
https://cherryontech-jupiter-jumpers.atlassian.net/browse/SCRUM-13

Related Story Card

Provide a link to the relevant story card.

Type of Changes

Feature update.

Acceptance Criteria

• User is taken to home page after creating account
• The confirmation modal appears after creating account
• The user can click 'get started' to close out the modal
• After refreshing, the user remains logged in
• The confirmation modal does not appear again after it is closed

Update Screenshots

Before

This was the view pre and post authentication

After

Modal appears after first authentication

UI reflects logged in state

Testing Instructions

1. Create an account
2. Make sure app directs you to home page (/)
3. View confirmation message modal
4. Close out modal
5. Make sure app reflects logged in state
6. Refresh to make sure you remain logged in (this takes a second so the logged out state will flash initially)

Learnings (Optional)

Document any things you learned or 'gotchas' you experienced.

[netlify]

✅ Deploy Preview for uncloud ready!

Name	Link
🔨 Latest commit	14bcff6
🔍 Latest deploy log	https://app.netlify.com/sites/uncloud/deploys/662d78c155bede0008025023
😎 Deploy Preview	https://deploy-preview-7--uncloud.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[jtkabenni]

To do:

• styling to match design, but wanted to see if storybook UI would impact this?
• wrote some files in js and need to convert to ts

[paola4]

I went through all the testing and acceptance criteria and it all checks out. The only thing I think we need to come back to later is that, when you refresh as a logged in user, the logged out state flashes for long enough that a user could interpret it as an error. It does keep the user logged in, though; it's just a brief flash (which Jenny points out in the PR notes).

[paola4]

To do:

* styling to match design, but wanted to see if storybook UI would impact this?

* wrote some files in js and need to convert to ts

I can add the components to Storybook, with updated styling to match the new wireframe!

[GinaCastromonte]

Looks great! The functionality worked according to the Jira needs. I did notice as well the state management is a little buggy when page is refreshed. I will take the task of fixing our auth/state management so that we can move on to the next sprint.