Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

B 22796 int #14917

Open
wants to merge 10 commits into
base: integrationTesting
Choose a base branch
from
Open

B 22796 int #14917

wants to merge 10 commits into from

Conversation

loganwc
Copy link
Contributor

@loganwc loganwc commented Feb 27, 2025

Agility ticket

Summary

There was an error when SC tries to make a move for a brand new user without their backup contact info saved.

Note

Other changes are matching main and int up so there aren't merge conflicts anymore.

How to test

  1. Create new customer
  2. enter name click next
  3. Logout and Login as a SC
  4. Search for that user
  5. Click create move
  6. Takes you to move creation page

@loganwc loganwc added G-Unit Scrum Team G INTEGRATION Slated for Integration Testing labels Feb 27, 2025
@loganwc loganwc self-assigned this Feb 27, 2025
@loganwc loganwc marked this pull request as ready for review February 27, 2025 21:23
@loganwc loganwc requested review from a team as code owners February 27, 2025 21:23
@loganwc loganwc mentioned this pull request Feb 28, 2025
Copy link
Contributor

@ajlusk ajlusk left a comment

Choose a reason for hiding this comment

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

Testing instructions work as written. I compared this to INT and this PR definitely solves the "Oops, Something went wrong" problem.

However, the page that now loads gives a different error on submission when following the testing steps. The customer never submitted a current or backup address and when the SC goes to fill that for them customer_updater.go is expecting those address to already exist (since it's an updater) and throws a nil pointer error.

The above issue may not be in scope but I couldn't find it documented.

The two changes to primeapiv2 should probably be removed to not re-introduce the conflict.

services.VLocation
planner route.Planner
Copy link
Contributor

@ajlusk ajlusk Feb 28, 2025

Choose a reason for hiding this comment

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

Other changes are matching main and int up so there aren't merge conflicts anymore.

I've been seeing the same conflict but it looks like someone else beat you to fixing this conflict. Both integrationTesting and main have vLocation last now.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

recently updated with int and it's still showing them for some reason 🤔

Copy link
Contributor

@ajlusk ajlusk Feb 28, 2025

Choose a reason for hiding this comment

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

I think accepting the version from your main branch into your INT branch (before the two matched) made 2c10ce7 the latest version.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
G-Unit Scrum Team G INTEGRATION Slated for Integration Testing
Development

Successfully merging this pull request may close these issues.

5 participants