I just recently discovered that having multiple ApiResponse attributes with the same status code but different descriptions breaks openapi endpoint.
The exception thrown was cryptic and took a bit to figure it out. The service calls don’t seem to break, but any usage of the openapi definition endpoint will.
I’m not sure if this is a limitation of the openapi schema or not. But, what I want to be able to do in my case is have for example, multiple attributes with different descriptions as there are multiple ways to throw status codes.
[ApiResponse(HttpStatusCode.Unauthorized, "This order doesn't belong to calling user.")]
[ApiResponse(HttpStatusCode.Unauthorized, "Invalid user.")]
If it’s a limitation of schema, i’ll just pass string.empty i guess