-
Notifications
You must be signed in to change notification settings - Fork 35
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
MAIN B-18313 Multi-Moves Profile Validation & Create a Move Btn Functionality #12041
Conversation
Missing commit hashes from integration branches |
You're correct. I was getting some crazy errors and weird white space issues so it was easier just to fix the files themselves via copy/paste. |
For these MM PRs into
Tryin' my best here. |
Bundle StatsHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset
View detailed bundle breakdownAdded
Removed
Bigger No assets were bigger Smaller No assets were smaller Unchanged
|
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.
Anything I saw different between the main and int PR was addressed in the int updates PR - all looks like it's matching.
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.
commits g2g
INTEGRATION PR
INTEGRATION PR - updates
Agility ticket
Summary
As we transition to allowing for multiple moves, we need to allow for the customer to validate their profile prior to starting a new move. If the service member does not have a previous move, then there's no need for them to validate their profile - technically it should already be current.
I went ahead and leveraged the
useLocation
hook to pass around a state value (needsToVerifyProfile
) when a user is validating their profile. At first I was usingsearchParams
but it felt a little clunky and was a lot harder to test, so I transitioned to using localstate
and passing thatstate
to the relevant components.This PR does the following:
state
object holding the current value ofneedsToVerifyProfile
Profile
component, conditional rendering will occur of links and an alert bannerHow to test Scenario 1 (previous moves)
Create a Move
buttonCreate a Move
button, andReturn to Dashboard
(instead ofReturn to Move
)Create a Move
button and you'll be navigated to the current home pageHow to test Scenario 2 (no previous moves)
http://milmovelocal:3000/?moveData=noMoves
into the urlCreate a Move
buttonScreenshots