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
Description
Using the useDelete hook, APIP-Admin only throw an 'Internal Server Error' error, even if the API return an error message.
For example, on the API side I have this:
This code return a 409 http status code, with the following body:
"@context": "/contexts/Error""@type": "hydra:Error""hydra:description": "My Error Message""hydra:title": "An error occurred"
Wich is at this point the intended behavior so there is no problem.
But then, on the admin side, when we delete the entity and we get a 409 response (in fact, no matter the status code, the result is the same for every HTTP errors), the APIP-admin dataProvider thrown an internal server error and does not take the hydra:description like it do with other methods (PUT, POST, GET...).
This is what is shown in the console when this occurs:
Error
at new HttpError (HttpError.js:33:23)
at eval (fetchHydra.js:53:39)
This may be a duplicate of this issue: Error message is not displayed on DELETE error #381, but as there where no activity since 2021, I didn't knew if it was ok to just add a comment or if I needed to create a new one
The text was updated successfully, but these errors were encountered:
API Platform Admin version(s) affected: 3.4.5
Description
Using the
useDelete
hook, APIP-Admin only throw an 'Internal Server Error' error, even if the API return an error message.For example, on the API side I have this:
This code return a 409 http status code, with the following body:
Wich is at this point the intended behavior so there is no problem.
But then, on the admin side, when we delete the entity and we get a 409 response (in fact, no matter the status code, the result is the same for every HTTP errors), the APIP-admin dataProvider thrown an
internal server error
and does not take the hydra:description like it do with other methods (PUT, POST, GET...).This is what is shown in the console when this occurs:
Aditionnal Context:
The text was updated successfully, but these errors were encountered: