-
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
B-21488: UB Allowance Warning Main #14503
Conversation
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.
Was there an upstream to this at one point? Has it been merged in? @TevinAdams
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.
Thanks for adding that upstream link back in, looks good there
Seeing an extra commit in this main PR that I don't see an equivalent change for in the integrationTesting branch
commit: 94b1504
@traskowskycaci It has been removed |
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.
Upstream merged, POA'd, issue fix pr present, commits good
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 match up now that the commit was removed! LGTM
Possible defect identified - excess risk does not qualify a second time. Getting this double checked |
marking draft for now |
|
We're bringing it up again as a possible missed requirement during standup tomorrow since it wasn't acknowledged in the ticket and tester doesn't remember if it was POA'd |
Cleared for release |
flaky test failing |
flaky tests failing again |
Merge After B-21675
B-21675 Main PR
Agility ticket
21488 INT PR 1
21488 INT PR 2
Summary
In this PR implementation is being added to evaluate excess weight for a UB shipment. Excess weight can be evaluated on shipments at 2 key points. When a shipment is approved and when a shipment is updated. On approval if the prime estimated weight exist then it will be evaluated. On update if the updated shipment has a prime estimated weight included.
For UB shipments, based on the AC of the story, when the primeEstimatedWeight or the primeActualWeight is within 10% or greater of the UBAllowance then excessWeight will be triggered until it has been acknowledged. Same flow of all other shipments.
Is there anything you would like reviewers to give additional scrutiny?
this article explains more about the approach used.
Verification Steps for the Author
These are to be checked by the author.
Verification Steps for Reviewers
These are to be checked by a reviewer.
Setup to Run the Code
How to test
3.Create a move using that address discussed above as one of the duty locations
Frontend
officeApp
class or custommin-width
styling is used to hide any states the would not be visible to the user.Backend
Database
Any new migrations/schema changes:
Screenshots
508 Compliance Check