You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition to this. When setting an enum as well (either using #[Property(enum: ['one', 'two', 'three']) or using Symfony-s Choice constraint) this "breaks" Swagger UI as well, as it just shows the oneOf and not the enum. When then removing this PHPDoc it does properly show the possible enum values. Which in turn also makes me wonder whether it would actually be valid to have a combination of enum and oneOf (as I can imagine that the enum cases all must be of the same type).
Description
Hi,
I have some code like this:
In the OpenAPI JSON this however is rendered into:
Which obviously is kinda wrong because of the
oneOf
which contains the same value ({"type": "string"}
) multiple times.Furthermore it would be nice if this union would automatically be converted into an enum, resulting in:
Additional context
No response
The text was updated successfully, but these errors were encountered: