DELETE hetzelfde behandelen als GET voor 400 bad request #292
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
github-actions
bot
added
Status: In bewerking
TimvdLippe
reviewed
Jan 22, 2026
Contributor
TimvdLippe
left a comment
TimvdLippe
left a comment
There was a problem hiding this comment.
De tests moeten worden geupdate, dat kan je doen met:
./linter/run-linter-tests.mjs --refresh
Overigens was voor GET het nog niet duidelijk tijdens het vorige TO of we dat moeten verplichten of niet. Dus ik denk dat voor DELETE dat we dezelfde analyse moeten doen.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Deze rule geldt alleen voor
GETindien er query parameters meegestuurd worden (die invalid kunnen zijn). Dit zou m.i. hetzelfde moeten werken voorDELETE; hier worden ook geen body parameters meegestuurd.