-
Notifications
You must be signed in to change notification settings - Fork 159
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
LG-15171 Fixes redirect for PUT #11545
Conversation
changelog: Bug Fixes, In-person proofing, fixes redirect for put for state id routes renaming
While this would successfully redirect requests to |
@aduth This is meant to address the fact that requests are going to that path. This change also affects the behavior we were seeing where the old route was being called in the first place, upon an unsuccessful form submission. We are still trying to understand exactly why this would be the case, but if you run through the test steps manually you can see the route isn't being hit anymore at all (not even as a redirect to the correct one). Edited to add more detail: what it seems like was happening is that having two routes mapping to the same controller action was causing weird behavior where the old route was being generated (I think it has to do with the |
Tested branch locally. I do not see |
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.
I reviewed and approved the PR. I also discussed it with Jenny for a bit on a call.
changelog: Bug Fixes, In-person proofing, fixes redirect for put for state id routes renaming
🎫 Ticket
Link to the relevant ticket:
LG-15171
🛠 Summary of changes
Fixes redirect for put for state id routes renaming. This is so that the transition to the new routes can be made without users still being directed to the old routes.
📜 Testing Plan
Provide a checklist of steps to confirm the changes.