Hardcoded parent constructor parameters on AbstractItemNormalizer

[DethCount]

core/src/Serializer/AbstractItemNormalizer.php

Line 75 in 81d276c

parent::__construct($classMetadataFactory, $nameConverter, null, null, \Closure::fromCallable([$this, 'getObjectClass']), $defaultContext);

[dunglas]

Hi, I don't understand the issue. Can you elaborate?

[DethCount]

You basically block users to use the full potential of this class.
I needed this parameter : PropertyTypeExtractorInterface $propertyTypeExtractor = null

[dunglas]

It’s on purpose. API Platform’s normalizers cannot work without the API Platform metadata system. You must not use a custom property type extractor here. However the API Platform metadata system can use you custom PropertyInfo implementations (and so it will be used by our normalizers).

[Toflar]

@dunglas I think I have the same issue here. Maybe missing something but when working with https://github.com/dunglas/doctrine-json-odm, the existing data that's in the database is correctly read in the ReadListener but then the DeserializeListener basically drops all the data as the serializer will create a new nested object.
What's the correct approach here then?

[lucasgranberg]

It’s on purpose. API Platform’s normalizers cannot work without the API Platform metadata system. You must not use a custom property type extractor here. However the API Platform metadata system can use you custom PropertyInfo implementations (and so it will be used by our normalizers).

I don't see how having access to PropertyInfo and ClassDiscriminatorResolver would get in the way of api-platform's custom normalizers. In my case I need these services in the normalizers becouse otherwise single table inheritance with discriminatorMapping won't work.