response-schema-problem
@azure-tools/typespec-azure-core/response-schema-problemWarn about operations having multiple non-error response schemas. If an operation has multiple response types for different success status codes, you may have forgotten to add @error to one of them.
โ Incorrect
Section titled โโ IncorrectโMultiple success responses with different body schemas:
model Widget { name: string;}
model WidgetCreated { name: string; creationResult: string;}
@errormodel Error { code: int32; message: string;}
model WidgetResponse { @statusCode status: 200; @body body: Widget;}
model WidgetCreatedResponse { @statusCode status: 201; @body body: WidgetCreated;}
op test(): WidgetResponse | WidgetCreatedResponse | Error;โ Correct
Section titled โโ CorrectโSingle success response schema with an error response:
@errormodel Error { code: int32; message: string;}
model WidgetResponse { @statusCode status: 200 | 201; @body body: Widget;}
op test(): WidgetResponse | Error;