You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions
Description
I have got a project set up with Gatsby and Springboot (Java) and I am able to do an API call from Gatsby to Springboot and create a user in my backend but if I get an error some reason Gatsby can't handle it such as I have a validation error that returns "User is not unique" but on Gatsby it just says Internal Server Error but if the API request is successful it works fine it says User Added. Does Gatsby not allow error handling? I am also using a proxy on Gatsby for CORS issues.
Reproduction Link
Non published
Steps to Reproduce
Axios function request
Send Invalid Data
Get response Internal Server Error
...
Expected Result
User has to be Unique
Postman response:
"timestamp": 1639313458756,
"status": 400,
"message": "Validation error",
"url": "/api/1.0/users",
"validationErrors": {
"username": "User has to be Unique"
}
Preliminary Checks
Description
I have got a project set up with Gatsby and Springboot (Java) and I am able to do an API call from Gatsby to Springboot and create a user in my backend but if I get an error some reason Gatsby can't handle it such as I have a validation error that returns "User is not unique" but on Gatsby it just says Internal Server Error but if the API request is successful it works fine it says User Added. Does Gatsby not allow error handling? I am also using a proxy on Gatsby for CORS issues.
Reproduction Link
Non published
Steps to Reproduce
...
Expected Result
User has to be Unique
Postman response:
"timestamp": 1639313458756,
"status": 400,
"message": "Validation error",
"url": "/api/1.0/users",
"validationErrors": {
"username": "User has to be Unique"
}
Actual Result
Internal Server Error
Environment
Config Flags
No response
The text was updated successfully, but these errors were encountered: