WIP: catch "route already exists in Publishing API" error #1211
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We had a situation earlier whereby Short URL Manager tried and failed to apply a redirect to an existing route, despite the 'override existing' field set to 'no'. The response was a 422 and no error message, which meant the user had to get in touch with support. We should investigate and fix the 'override existing' check, as well as do a better job at surfacing errors. I tried and failed to recreate the scenario here in several different test files, but it may be useful as a starting point for whoever picks up the card. Trello: https://trello.com/c/PVcAt5Ll/3178-surface-path-reserved-errors-in-ui
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We had a situation earlier whereby Short URL Manager tried and failed to apply a redirect to an existing route, despite the 'override existing' field set to 'no'. The response was a 422 and no error message, which meant the user had to get in touch with support.
We should investigate and fix the 'override existing' check, as well as do a better job at surfacing errors.
I tried and failed to recreate the scenario here in several different test files, but it may be useful as a starting point for whoever picks up the card.
Trello: https://trello.com/c/PVcAt5Ll/3178-surface-path-reserved-errors-in-ui
Follow these steps if you are doing a Rails upgrade.