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

INT-B-19226 Revert and redo of form changes #13609

Merged
merged 7 commits into from
Sep 4, 2024

Conversation

brooklyn-welsh
Copy link
Contributor

Agility ticket

Relevant INT PRs

#13474
#13548
#13567

Summary

This PR changes customer onboarding and move creation forms in MilMove to label required fields with light grey "Required" text, while getting rid of the existing "Optional" text that currently accompanies optional fields. While this was handled with the other INT PRs, the method used changed behavior across the entire app, which was not in the story scope. Now only forms on the Customer side should be affected.

How to test

Please follow the steps in the relevant INT PRs, but basically, check all customer side onboarding and move forms to check that all form fields that are needed to submit show a "Required" light grey help label, and that no "Optional" labels are left over.

@brooklyn-welsh brooklyn-welsh added ByteSize M&Ms Team ByteSized M&Ms INTEGRATION Slated for Integration Testing labels Aug 30, 2024
@brooklyn-welsh brooklyn-welsh marked this pull request as ready for review August 30, 2024 19:54
@brooklyn-welsh brooklyn-welsh requested a review from a team as a code owner August 30, 2024 19:54
@taeJungCaci
Copy link
Contributor

I'm seeing required and optional labels for dimensions in boat shipment form and mobile shipment from. Is this correct?
image

@brooklyn-welsh
Copy link
Contributor Author

I'm seeing required and optional labels for dimensions in boat shipment form and mobile shipment from. Is this correct? image

Good catch, definitely not, I'm assuming something weird happened with merge conflicts that didn't show up while I had the server running since it wasn't like this in my MAIN branch, will edit real quick with a fix

@taeJungCaci
Copy link
Contributor

also not sure if this is related to your changes, but the fields styling got changed for city and state - One is from Main and other is INT. Might be someone else's changes, but maybe you might know:
image
image

@brooklyn-welsh
Copy link
Contributor Author

also not sure if this is related to your changes, but the fields styling got changed for city and state - One is from Main and other is INT. Might be someone else's changes, but maybe you might know: image image

Yeah this is currently only in INT and is a result of change from Ricky I believe, looks like there's a story that changes it to where the user can just put in their address and the rest auto fills or something like that. From what I can tell that is supposed to be like that, had to refactor a bunch of tests to get them to work with the new UI after changing the optional labels.

Copy link
Contributor

@taeJungCaci taeJungCaci left a comment

Choose a reason for hiding this comment

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

LGTM

@taeJungCaci
Copy link
Contributor

taeJungCaci commented Sep 3, 2024

I hope you are tracking all the changes with all theses PRs because I can already tell this MAIN PR is gonna be a massive pain 😭 .

Copy link
Contributor

@WeatherfordAaron WeatherfordAaron left a comment

Choose a reason for hiding this comment

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

lgtm

@brooklyn-welsh brooklyn-welsh merged commit faf61b3 into integrationTesting Sep 4, 2024
28 of 29 checks passed
@brooklyn-welsh brooklyn-welsh deleted the INT-B-19226-redo branch September 4, 2024 15:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ByteSize M&Ms Team ByteSized M&Ms INTEGRATION Slated for Integration Testing
Development

Successfully merging this pull request may close these issues.

3 participants