-
-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: move server api method invocation out of try-catch for parsing #6890
Merged
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
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## unstable #6890 +/- ##
============================================
- Coverage 62.75% 62.75% -0.01%
============================================
Files 578 578
Lines 61347 61344 -3
Branches 2114 2116 +2
============================================
- Hits 38498 38495 -3
Misses 22811 22811
Partials 38 38 |
Performance Report✔️ no performance regression detected Full benchmark results
|
wemeetagain
approved these changes
Jun 20, 2024
🎉 This PR is included in v1.20.0 🎉 |
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.
Motivation
Noticed method invocation calls are part of try-catch for parsing, in the case the server throws any non-
ApiError
it would still result in a 400 response which is not desired as this status code would indicate a client issue while if we throwError
on the server it indicates some internal issue and should be a 500 response.This also simplifies the server handler a bit and better separates parsing from method invocation.
Description
Move server api method invocation out of try-catch for parsing