Antoine Bluchet

just add this value to your serializer context on the targetted operation ? This has security impacts we can't ignore the IRI.

doesn't: ``` #[ApiResource(normalizationContext: [AbstractObjectNormalizer::EXCLUDE_FROM_CACHE_KEY => ['iri']]); ``` works? Not having the IRI inside a collection makes that you have the same cache for every item of that collection. When using...

Should we target another branch then main though? @dunglas any opinion?

thanks @DaedalusDev @bendavies !

Hi, ` ApiPlatform\Util\Inflector` is deprecated. We should definitely always go to the new inflector or the one you choose please open a PR.

I don't understand your name converter should end-up being injected inside https://github.com/symfony/symfony/blob/1f90bc30c32b375ed2cdc3234f56d26b8b99cb53/src/Symfony/Component/Serializer/NameConverter/MetadataAwareNameConverter.php. About the serializer being altered, maybe that's because of the serializer alias https://github.com/api-platform/core/blob/main/src/Symfony/Bundle/Resources/config/api.xml#L12 ? @dunglas is this intended?

please update to latest 3.2. we should probably just use the same logic that I see at https://github.com/api-platform/core/blob/a749fe8494a5b3ca41139a418ed1e29c3e7b33a6/src/GraphQl/State/Provider/ReadProvider.php#L71 I would be curious to see what test fail on this use...

https://github.com/api-platform/core/pull/5882/files#diff-1f34d8685c9bbcc2037ef47c41cb6dac916a0fe6fc06e2047b9635e35fa13527R396 it's missing jsonapi/hal normalizers indeed.

Indeed, I plan to continue working on this mid-june.

merging now that the CI is all green, it's still missing some features (security / filters) and it'll be easier to review afterwards.