Generate Workflows Execution SDK #226
Annotations
10 warnings
|
|
|
openapi/openapi_0.yaml#L42
validation warn: [line 42] operation-success-response - Operation `getExecutions` uses an `integer` instead of a `string` for response code `200`
|
|
openapi/openapi_0.yaml#L42
validation warn: [line 42] operation-success-response - Operation `getExecutions` uses an `integer` instead of a `string` for response code `500`
|
|
openapi/openapi_0.yaml#L70
validation warn: [line 70] operation-success-response - Operation `createExecution` uses an `integer` instead of a `string` for response code `201`
|
|
openapi/openapi_0.yaml#L70
validation warn: [line 70] operation-success-response - Operation `createExecution` uses an `integer` instead of a `string` for response code `400`
|
|
openapi/openapi_0.yaml#L70
validation warn: [line 70] operation-success-response - Operation `createExecution` uses an `integer` instead of a `string` for response code `401`
|
|
openapi/openapi_0.yaml#L70
validation warn: [line 70] operation-success-response - Operation `createExecution` uses an `integer` instead of a `string` for response code `500`
|
|
openapi/openapi_0.yaml#L112
validation warn: [line 112] operation-success-response - Operation `getExecution` uses an `integer` instead of a `string` for response code `200`
|
|
openapi/openapi_0.yaml#L112
validation warn: [line 112] operation-success-response - Operation `getExecution` uses an `integer` instead of a `string` for response code `500`
|
|
openapi/openapi_0.yaml#L146
validation warn: [line 146] operation-success-response - Operation `updateExecution` uses an `integer` instead of a `string` for response code `204`
|
The logs for this run have expired and are no longer available.
Loading