use a less wrong scheam for save-draft (#402)

Co-authored-by: burnettk <burnettk@users.noreply.github.com>
This commit is contained in:
Kevin Burnett 2023-07-25 10:24:48 -07:00 committed by GitHub
parent a4ceb982ea
commit 77f922f675
1 changed files with 8 additions and 1 deletions

View File

@ -1949,7 +1949,7 @@ paths:
content: content:
application/json: application/json:
schema: schema:
$ref: "#/components/schemas/ProcessGroup" $ref: "#/components/schemas/AwesomeUnspecifiedPayload"
responses: responses:
"200": "200":
description: One task description: One task
@ -3160,6 +3160,13 @@ components:
report_metadata: report_metadata:
nullable: false nullable: false
$ref: "#/components/schemas/ReportMetadata" $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: ReportMetadata:
properties: properties:
columns: columns: