Fix HTTP DELETE endpoints to use query parameters #810
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.
Summary
Changes
Backend (6 files, 8 DELETE methods)
Controllers updated:
acts.py- DELETE endpoint now uses query parametercast.py- DELETE endpoint now uses query parametercharacters.py- Both DELETE endpoints (Character and CharacterGroup) now use query parameterscues.py- Both DELETE endpoints (CueType and Cue) now use query parametersmicrophones.py- DELETE endpoint now uses query parameterscenes.py- DELETE endpoint now uses query parameterImplementation:
escape.json_decode(self.request.body)toself.get_argument("id", None)int()conversion with try/except blocksFrontend (2 files, 9 DELETE calls)
Files updated:
show.js- 7 DELETE API callsscript.js- 2 DELETE API calls (including multi-parameter DELETE_CUE)Implementation:
URLSearchParamsfor query parameter constructionDELETE_SCRIPT_REVISIONWhy This Matters
Testing
Deployment Notes
This is a breaking change - old clients will receive 400 errors when attempting DELETE operations.
🤖 Generated with Claude Code