Specs containing or fail on alternate cases - this was working in 2.0.0-alpha28. Of course, the swagger definition can only show one of the or alternatives only, but any request payload that conforms to the spec should (and did) work - could this behaviour be reverted back please?
eg. in the below, the definition of the linux-group would display in the swagger page, but body params containing the windows group would fail, eg {:group {:linux-id 1}} - succeeds, {:group {:windows-id "1"}} - fails.
Library Version(s)
2.0.0-alpha30
Problem
Specs containing
or
fail on alternate cases - this was working in 2.0.0-alpha28. Of course, the swagger definition can only show one of theor
alternatives only, but any request payload that conforms to the spec should (and did) work - could this behaviour be reverted back please?eg. in the below, the definition of the linux-group would display in the swagger page, but body params containing the windows group would fail, eg
{:group {:linux-id 1}}
- succeeds,{:group {:windows-id "1"}}
- fails.