MAIN B-20316 - Pro Gear Weights in Prime V3 API

[ajlusk]

B-20316

INT PR

Summary

Pro Gear Weights were getting added to the Prime V1 and Prime V2 APIs at the same time Prime V3 was getting created. That timing caused those fields to not make it into Prime V3. Later, the Simulator was updated to use Prime V3 in places that used Pro Gear Weights and this issue became much more noticeable. <- All of this was in tasks assigned to our team.

Brooklyn noticed this issue and fixed Prime V3 to accept and persist Pro Gear Weights. This ticket returns those stored values.

I was eager to move this to PI 24.5 so it could be fixed before Home Safe switches to V3.

Verification Steps for the Author

These are to be checked by the author.

• Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
• Have the Agility acceptance criteria been met for this change?

Verification Steps for Reviewers

These are to be checked by a reviewer.

• Has the branch been pulled in and checked out?
• Have the BL acceptance criteria been met for this change?
• Was the CircleCI build successful?
• Has the code been reviewed from a standards and best practices point of view?

Setup to Run the Code

• Instructions for starting storybook
• Instructions for starting the MilMove application
• Instructions for running tests

How to test

1. Access the
2. Login as a

Frontend

• There are no aXe warnings for UI.
• This works in Supported Browsers and their phone views (Chrome, Firefox, Edge).
• There are no new console errors in the browser devtools.
• There are no new console errors in the test output.
• If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.
• This change meets the standards for Section 508 compliance.

Backend

• Code follows the guidelines for Logging.
• The requirements listed in Querying the Database Safely have been satisfied.

Database

Any new migrations/schema changes:

• Follows our guidelines for Zero-Downtime Deploys.
• Have been communicated to #g-database.
• Secure migrations have been tested following the instructions in our docs.

Screenshots

[CoryKleinjanCACI]

Changed match INT.

[r-mettler]

good