Closed TheOddler closed 1 year ago
That's a very interesting issue. Great digging! PR Welcome
@TheOddler Is this issue still there in the latest release? I would appreciate a PR to fix this.
I'll have to check it out. Haven't had time/energy to look at it yet.
PR welcome
It looks like the openapi output is incorrect when using multiple
parseAlternative
s.We have the following code:
Which produces the following openapi definition:
This does not include the
userId
as a field.When I remove one of the
parseAlternative
s:The openapi definition does include the
userId
: