Generate Workflows Definition SDK #260
Annotations
10 warnings
|
|
|
openapi/openapi_0.yaml#L22
validation warn: [line 22] operation-tag-defined - the `get` operation at path `/v1/workflows/limits/max-allowed` contains a tag `Workflows`, that is not defined in the global document tags
|
|
openapi/openapi_0.yaml#L23
validation warn: [line 23] operation-success-response - Operation `getMaxAllowedLimit` uses an `integer` instead of a `string` for response code `200`
|
|
openapi/openapi_0.yaml#L23
validation warn: [line 23] operation-success-response - Operation `getMaxAllowedLimit` uses an `integer` instead of a `string` for response code `500`
|
|
openapi/openapi_0.yaml#L46
validation warn: [line 46] operation-tag-defined - the `get` operation at path `/v1/workflows/definitions` contains a tag `Workflows`, that is not defined in the global document tags
|
|
openapi/openapi_0.yaml#L47
validation warn: [line 47] operation-success-response - Operation `getDefinitions` uses an `integer` instead of a `string` for response code `200`
|
|
openapi/openapi_0.yaml#L47
validation warn: [line 47] operation-success-response - Operation `getDefinitions` uses an `integer` instead of a `string` for response code `500`
|
|
openapi/openapi_0.yaml#L103
validation warn: [line 103] operation-tag-defined - the `post` operation at path `/v1/workflows/definitions` contains a tag `Workflows`, that is not defined in the global document tags
|
|
openapi/openapi_0.yaml#L139
validation warn: [line 139] operation-success-response - Operation `createDefinition` uses an `integer` instead of a `string` for response code `200`
|
|
openapi/openapi_0.yaml#L139
validation warn: [line 139] operation-success-response - Operation `createDefinition` uses an `integer` instead of a `string` for response code `400`
|
The logs for this run have expired and are no longer available.
Loading