feat(api-raw): raise a 404 Not Found error when a resource is missing in the study #2078
Conversation
This file contains 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
mabw-rte
suggested changes
Jun 27, 2024
laurent-laporte-pro
force-pushed
the
feature/improve-raw-api-error-handling
branch
from
49be693 to
27a60d3
Compare
mabw-rte
approved these changes
Jun 27, 2024
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.
This PR enhances the error management for the
GET /v1/studies/{uuid}/rawendpoint. It now returns a 404 Not Found error if a resource within the study is unavailable, replacing the previous 500 error, which was not ideal.Additionally, this Pull Request refines the code structure and style in the
test_binding_constraints.pyfile, making it more straightforward.These modifications are necessary for issue #2077.