We are now seeing validation errors requiring the format of response code to be an object:
"value": 200
This is related to undocumented behavior for non discriminated union types spanning primitive types and defined models. Update the service spec to document the response code as a string - we continue to validate proper integer or the keyword "default".
We are now seeing validation errors requiring the format of response code to be an object:
This is related to undocumented behavior for non discriminated union types spanning primitive types and defined models. Update the service spec to document the response code as a string - we continue to validate proper integer or the keyword "default".