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

MB-14374 Remove value from ppm_shipment_status enum (NEEDS_CLOSE_OUT) #9506

Merged
merged 2 commits into from
Nov 3, 2022

Conversation

Ryan-Koch
Copy link
Contributor

Jira ticket for this change

Summary

This removes the NEEDS_CLOSE_OUT status we added previously for the ppm_shipment_status enum on ppm_shipment. It turned out there were already statuses to handle what we needed.

Approach

For safety reasons it seemed best to go ahead and go about this the following way:

  1. Rename the current thing
  2. Create a replacement type
  3. Make sure we don't have any of the old values in the DB (we shouldn't but just in case)
  4. Apply the new type to the status field on the table
  5. Drop the old type

Let me know if there's a different way we should go about it.

Verification Steps for 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)
  • Request review from a member of a different team.
  • Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers

These are to be checked by a reviewer.

Frontend

  • User facing changes have been reviewed by design.
  • There are no aXe warnings for UI.
  • This works in Supported Browsers and their phone views (Chrome, Firefox, IE, 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.

Backend

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

@robot-mymove
Copy link

robot-mymove commented Nov 1, 2022

Messages
📖 🔗 MB-14374

Generated by 🚫 dangerJS against 6ff68c9

@Ryan-Koch Ryan-Koch requested a review from a team November 3, 2022 15:05
@Ryan-Koch Ryan-Koch marked this pull request as ready for review November 3, 2022 15:05
@Ryan-Koch Ryan-Koch requested a review from a team November 3, 2022 15:05
Copy link
Contributor

@mandaem mandaem left a comment

Choose a reason for hiding this comment

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

LGTM, ex. I no longer see NEEDS_CLOSE_OUT enum in ppm_shipment_status

Copy link
Contributor

@reggieriser reggieriser left a comment

Choose a reason for hiding this comment

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

LGTM! Migration worked fine, and AFAIK, this is the preferred way of removing a value from an enum.

@Ryan-Koch Ryan-Koch merged commit bf3f576 into master Nov 3, 2022
@Ryan-Koch Ryan-Koch deleted the MB-14374 branch November 3, 2022 16:55
felipe-lee added a commit that referenced this pull request Jun 5, 2023
Needed for the react-router update because of [ #9506 - Fix inadvertent support for partial dynamic parameters](remix-run/react-router#9506).

JIRA Ticket: MB-15974
Co-authored-by: Kyle Hill <[email protected]>
felipe-lee added a commit that referenced this pull request Jun 6, 2023
Needed for the react-router update because of [ #9506 - Fix inadvertent support for partial dynamic parameters](remix-run/react-router#9506).

JIRA Ticket: MB-15974
Co-authored-by: Kyle Hill <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants