use a less wrong scheam for save-draft (#402)
Co-authored-by: burnettk <burnettk@users.noreply.github.com>
This commit is contained in:
parent
2b2234844c
commit
a18cf04b46
|
@ -1949,7 +1949,7 @@ paths:
|
|||
content:
|
||||
application/json:
|
||||
schema:
|
||||
$ref: "#/components/schemas/ProcessGroup"
|
||||
$ref: "#/components/schemas/AwesomeUnspecifiedPayload"
|
||||
responses:
|
||||
"200":
|
||||
description: One task
|
||||
|
@ -3160,6 +3160,13 @@ components:
|
|||
report_metadata:
|
||||
nullable: false
|
||||
$ref: "#/components/schemas/ReportMetadata"
|
||||
# if we pass a payload and give it a field of the wrong type (say we pass a field with value null and it wants a string)
|
||||
# it will fail validation and not pass the request to the controller. that is generally not desirable
|
||||
# until we take a closer look at the schemas in here.
|
||||
AwesomeUnspecifiedPayload:
|
||||
properties:
|
||||
anythingyouwant:
|
||||
type: string
|
||||
ReportMetadata:
|
||||
properties:
|
||||
columns:
|
||||
|
|
Loading…
Reference in New Issue