[Question]: Assert/Choice overrides enum

[ggroy12]

Version

4.20

Question

If I specify an Assert/Choice for a property in my DTO, it overrides the enum property.
How can I indicate the priority on an enum, so that the documentation displays exactly the enum from the OA\Property property, and not the specified value from the assertion?

That is, valid values ​​should be value1, value2, value3, value4.
But the documentation should only show value3 and value4.
Consider these legacy values ​​that are still supported but should not be used by new users.

Additional context

No response

[DjordyKoert]

There is currently no way to override this behaviour unfortunately. I do agree that manually defining a schema (using OA from swagger-php) should take priority in these cases.

A schema should only be augmented (from Symfony attributes in this example) if the property has not been set by the user.

[jetrodn]

It seems to be only for property of type string