PUT with embedded relation, no route matches "<int>", ItemNormalizer bug ?

[VaN-dev]

Hello,

i'm facing a bug when submitting a PUT request with embedded relation :

data sample posted :

array:7 [
  "@context" => "/app_dev.php/contexts/Staking"
  "@id" => "/app_dev.php/stakings/10"
  "@type" => "Staking"
  "id" => 10
  "tournaments" => array:1 [
    0 => array:4 [
      "@id" => "/app_dev.php/staking_tournaments/3"
      "@type" => "StakingTournament"
      "id" => 3
      "tournament" => "/app_dev.php/tournaments/1"
    ]
  ]
  "name" => "Staking #111"
  "mode" => "simple"
]

api-platform returns me the following error :

{
    "@context":"\app_dev.php/contexts/Error",
    "@type":"Error",
    "hydra:title":"An error occurred",
    "hydra:description":"No route matches "3".", 
    ...
}

The error is caused by src\Serializer\ItemNormalizer.php, line 36, using $data['id'] instead of $data['@id']. In my case, $data['id'] is supposed to be an integer, the PK in database, not a resource URL.

[Simperfit]

Could you please test the PR ?

[dunglas]

I think this bug is related with how embed relations are handled. @VaN-dev, can you open a PR with a failing Behat test?

[dunglas]

Can you also post the full stack trace, because src\Serializer\ItemNormalizer.php should not be called at all (the JSON-LD normalizer must be used).

[Simperfit]

I've added the failing behat test case and this happen when sending an int in iri using the header to be application/json like in this case.

IMO there is two ways to correct this :

• settled that anyway an iri should be in @id and not in the id.
• test if it's an iri before using the iriConverter