Antoine Bluchet

Either you have the operation inside the context or you need to use the ResourceMetadataFactory basicaly it's like: https://github.com/api-platform/core/blob/ad2d5a78f36273b706e180ebdbdf1617d952138d/src/Serializer/AbstractItemNormalizer.php#L799-L801

Not sure that this is correct, uri variables are present for the main resource, but when it's a relation we can't know for sure that uri variables are the one...

> If it's mandatory for ApiResources to have ApiProperty identifiers starting from a specific ApiPlatform version, please let me know. ApiResource must have an identifier if there's one in the...

Thanks for your work @ttskch! I was on holiday and I'll take time to see how everything fits here, I'll come back to that asap.

So, the main issue here is that we multiply the JSON Schemas for a given resource which is really heavy work for no much gain. I don't have much time...

We need to use `$id` to have base schemas that each resource schema would extend: https://json-schema.org/draft/2020-12/json-schema-core#id-keyword. This is not so easy to implement but I'll willing to give a shot...

should be fixed in 4.2

Can't you set `skip_null_values` to `false` in the denormalizer context? Maybe that it should be the default during denormalization (@dunglas)

See https://github.com/api-platform/core/pull/6485#issuecomment-2326565170 for this PR's resolution

its possible that this is actually fixed but indeed it'll be way easier using the 4. version