-
Notifications
You must be signed in to change notification settings - Fork 184
Fix 4xx error handling #195
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 4xx error handling #195
Conversation
Codecov Report
@@ Coverage Diff @@
## master #195 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 14 16 +2
Lines 949 984 +35
=========================================
+ Hits 949 984 +35
Continue to review full report at Codecov.
|
I've tried fixing the Lint issues. When I run them locally, they don't complain of anything, but on github they are throwing errors. |
Regarding the linting issues, you probably don't have the correct dev dependencies. |
@leszekhanusz Thanks. It is fixed now. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #195 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 16 16
Lines 978 985 +7
=========================================
+ Hits 978 985 +7 ☔ View full report in Codecov by Sentry. |
I made a refactor in order to avoid checking for the content_type. Could you please check that it is ok for you ? |
To resume, here was the situation previously:
Now we have:
Note that we still set an |
Looks good to me. |
How to get error info following a 400 error response. I get only a bas request line vs Details when using any Api platform. For example, running this query in Insomnia or Postman i get the useful error message: Using the gql client:
The only output i get and stacktrace:
Am i missing something? Thank you @leszekhanusz |
@yassinsameh Please open another issue when you have a problem instead of adding a comment to a closed PR. Concerning your problem, gql error handling is explained here. |
Fixes #194