You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The swagger definitions don't seem to have error codes/schema definitions. For example, PacketAnalyzers POST doesn't include the 400 error in the list of responses:
post:
tags:
- PacketAnalyzers
summary: Create a packet analyzer
description: Create a new packet analyzer.
operationId: CreatePacketAnalyzer
parameters:
- in: body
name: analyzer
description: New packet analyzer
required: true
schema:
$ref: '#/definitions/PacketAnalyzer'
responses:
"201":
description: Created
headers:
Location:
type: string
description: URI of created analyzer
schema:
$ref: '#/definitions/PacketAnalyzer'
When using the go-swagger generated API this results in the API reporting it received an unsupported/unexpected response when an error occurs.
The text was updated successfully, but these errors were encountered:
The swagger definitions don't seem to have error codes/schema definitions. For example, PacketAnalyzers POST doesn't include the 400 error in the list of responses:
When using the go-swagger generated API this results in the API reporting it received an unsupported/unexpected response when an error occurs.
The text was updated successfully, but these errors were encountered: