Repository navigation
Show why a new show was refused (release 1.11.1) - #20
Merged
Merged
Conversation
The new-show route answered with the error's own status (400/409), but the page only swaps a 422 into the modal, so the reason was discarded. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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
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.
Creating a show that the server refused (folder name already used, invalid name, unwritable shows folder) answered 400/409, but the page only swaps a 422 into the modal, so the reason was dropped and the user saw a bare "Something went wrong."
POST /ui/showsnow answers 422 for every refusal, so the dialog shows the reason under the field.Full suite: 1477 pass. After merge, tagging
v1.11.1publishes the image.🤖 Generated with Claude Code