Improve error handling for item retrieval #14382
Draft
+5
−1
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
Fix: Return 404 for non-existent items instead of null response Previously, valid ID formats with non-existent items returned 200 OK with null values, creating ambiguous API responses. Now properly returns 404 Not Found when items don't exist in the database.
Contributor
📝 Docs previewLast commit e5f643c at: https://0b6b9b2f.fastapitiangolo.pages.dev |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fix: Return 404 for non-existent items instead of null response
Previously, valid ID formats with non-existent items returned 200 OK with null values, creating ambiguous API responses. Now properly returns 404 Not Found when items don't exist in the database.