What about providing@ExclusionPolicy in JMS-serializer manner? There is opened PR#19374 for that.

The plans to improve the Serializer are in#19374 (comment).

@dunglas Do you plan to finish this PR before 4.3 feature freeze?

Yes I'll try to finish it tomorrow

Can this annotation be aPropertyInfo component feature instead ? Which remove the property from the getProperties method if needed ?

So other components / library can profit from this metadata as well ?

IMHO, the@ignore annotation should be owned by the Serializer component because we may want to exclude the property for the Serializer but to include it for anything else.

And about properties extraction, after trying to finish#28775, I figured that the interface about extracting properties to (un-)serialize must belong to the Serializer component and we could also ship a default implementation built on top of the PropertyInfo component.

Then, we could use decorators, to implement@Ignore,@ExclusionPolicy,@Expose,@Since,@Until, etc... We also be able to move the@Groups into an implementation of this interface.

This would move the logic of getting which properties must be (un-)serialize out of Normalizer and improve a lot the S.O.L.I.D.ity of the Serializer component and help to deprecate theGetSetMethodNormalizer, thePropertyNormalizer, theAbstractObjectNormalizer and theAbstractNormalizer.

@joelwurtz,@dunglas let's talk about this at Symfony Live :)

👍 for talking about this at SymfonyLive, as for the annotation, i don't see a problem on having it on Serializer only by using a dedicated PropertyInfo extractor chain ?

A lot of the annotations that you propose can be also useful in the context of theAutomapper if this component is wanted, i would prefer having those in the symfony property info component as decorator, so other components can also profit of this.

Also if this gets merged#30704 and there is a direct link between PropertyAccess and ProperyInfo component in the future, those annotation + decorators could be used in many place where we want to restrict property. Like in theForm /Validator /Workflow compoenent, this would allow to restrict some properties to be used when using a property path, and avoid exposing some data.

but let's discuss this at symfony live like you said,

Just talk with@dmaicher and i think it would be wise to do/finish#30818 (or at least the basics) first before doing this. WDYT@dunglas ?

Any updates regarding this?

Tests added and comments resolved. This PR should be good to be merged now.
As the refactoring work on the Serializer is stuck for months (#30818), I propose to move forward regarding this PR, we'll be able to refactor this later anyway if needed.

(and fixed deps=low)

This one is ready to be merged.

Thank you@dunglas.

Doc issue theresymfony/symfony-docs#13585 I am actually tring to add the documentation