Can GraphQL Mutation API handle custom type params...
# supportb
boogiecoco.
07/28/2023, 7:58 PMCurrently, we're running into the issue of passing a ton of properties into our GraphQL mutations that are of type
String!r
rahul1
07/28/2023, 8:02 PMHi @boogiecoco. , just so I understand, do you have an example of a mutation you're doing right now, and how it would ideall look with custom types?
b
boogiecoco.
07/28/2023, 8:07 PMHere's one example at the top of my head where it could be useful:
export const CREATE_COMMUNICATION = gql`
mutation CreateCommunication(
$payload: [CommunicationPayloadInput!]!
) {
createCommunication(
communication: {
resourceType: "Communication"
payload: $payload
}
) {
id
}
}
`
boogiecoco.
07/28/2023, 8:12 PMAs opposed to:
export const CREATE_COMMUNICATION = gql
Copy code
mutation CreateCommunication(
$payloadContentString: String!
$payloadContentAttachmentTitle: String!
$payloadContentAttachmentUrl: String!
) {
createCommunication(
communication: {
resourceType: "Communication"
payload: [
{
contentString: $payloadContentString,
contentAttachment: {
title: $payloadContentAttachmentTitle,
url: $payloadContentAttachmentUrl
}
}
]
}
)r
rahul1
07/28/2023, 8:42 PM@boogiecoco. Good news! I think I have a solution for you.
rahul1
07/28/2023, 8:44 PMSo you can't define custom types on the client, since the server maintains the GQL introspection schema.
The good news is that Medplum generates GraphQL types not just for the top-level resource types, but also for the complex inner types (AKA "backbone elements")
rahul1
07/28/2023, 8:44 PMI just tested this query on graphiql.medplum.com
Copy code
mutation CreatComm($payload: [CommunicationPayloadCreate!]!) {
CommunicationCreate(res: {
resourceType: "Communication",
status: "draft",
payload: $payload
}) {
id,
resourceType,
payload {contentString, contentAttachment {url}}
}
}rahul1
07/28/2023, 8:48 PMThe type name for the parameter would be
<inner-type-name>Createb
boogiecoco.
07/28/2023, 9:05 PMThat works for us, thank you !
156 Views