From 77f922f6750bb0e10861685fbb077e11bd69f5bb Mon Sep 17 00:00:00 2001 From: Kevin Burnett <18027+burnettk@users.noreply.github.com> Date: Tue, 25 Jul 2023 10:24:48 -0700 Subject: [PATCH] use a less wrong scheam for save-draft (#402) Co-authored-by: burnettk --- spiffworkflow-backend/src/spiffworkflow_backend/api.yml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/spiffworkflow-backend/src/spiffworkflow_backend/api.yml b/spiffworkflow-backend/src/spiffworkflow_backend/api.yml index 8db6c1d40..e13384121 100755 --- a/spiffworkflow-backend/src/spiffworkflow_backend/api.yml +++ b/spiffworkflow-backend/src/spiffworkflow_backend/api.yml @@ -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: