Mark McDonald
06/19/2020, 1:23 AMcreate_cloud_hook
mutation?
I'm getting the following error:
{
"graphQLErrors": [
{
"path": [
"create_cloud_hook"
],
"message": "Expected type JSON, found {to: \"<mailto:test@test.com|test@test.com>\"}; 'ObjectValueNode' object has no attribute 'value'",
"extensions": {
"code": "INTERNAL_SERVER_ERROR",
"exception": {
"message": "Expected type JSON, found {to: \"<mailto:test@test.com|test@test.com>\"}; 'ObjectValueNode' object has no attribute 'value'",
"locations": [
{
"line": 2,
"column": 146
}
],
"path": null
}
}
}
],
"networkError": null,
"message": "GraphQL error: Expected type JSON, found {to: \"<mailto:test@test.com|test@test.com>\"}; 'ObjectValueNode' object has no attribute 'value'"
}
I'm pulling the mutation straight out of the docs here
This was previously working for me.mutation {
create_cloud_hook(input: {type: EMAIL, name: "Example", version_group_id: "version-group-id", states: ["Running"], config: {to: "<mailto:test@test.com|test@test.com>"}}) {
id
}
}
Jeremiah
06/19/2020, 1:29 AMmutation {
create_cloud_hook(input: {type: EMAIL, name: "Example", version_group_id: "abc", states: ["Running"], config: "{\"to\": \"<mailto:test@test.com|test@test.com>\"}"}) {
id
}
}
{to: "<mailto:test@test.com|test@test.com>"}
. The updated server is complaining a lot about invalid objects if I try to force the old behavior, so I think this was considered a bug in the implementation. I’ll update the docs. Thanks for pointing this out!Mark McDonald
06/19/2020, 1:58 AMto
wasn't actually in quotes isn't valid json. It's strange that that ever worked.Jeremiah
06/19/2020, 1:59 AM