Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

dataProvider delete method only throw Internal Server Error message for errors

Open
#523 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
react, typescript
Domain
api, frontend

Research direction

Start with the dataProvider delete path and the fetchHydra.js and HttpError.js locations shown in the console stack. Compare delete error handling with the PUT, POST, and GET paths, then verify that an HTTP error response containing hydra:description produces that message instead of the generic internal server error.

Written by the indexing model from the issue text.

Description

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:

  throw new EntityDeleteForeignKeyException(
      $this->translator->trans(
          'error.entity.my_entity.delete.has_foreign_key',
          [
              '%my_entity%' => $item->value,
              '%entity_linked%' => $this->translator->trans('entity.my_other_entity'),
          ]
      )
  );

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)

Aditionnal Context:

Dominant language
TypeScript
Stars
516
Forks
134
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from api-platform/admin

All issues in api-platform/admin

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.