Clojurians Log v2

Q: has anyone created a fn that coerces arguments using the GQL type definitions available in :com.walmartlabs.lacinia.constants/parsed-query?

How would you interpret this?

"{\"errors\":[{\"message\":\"Failed to parse GraphQL query.\",\"extensions\":{\"errors\":[{\"locations\":[{\"line\":1,\"column\":null}],\"message\":\"mismatched input '\\\"query\\\"' expecting {'query', 'mutation', 'subscription', '...', NameId}\"},{\"locations\":[{\"line\":1,\"column\":null}],\"message\":\"mismatched input '\\\"b\\\"' expecting {'query', 'mutation', 'subscription', '...', NameId}\"},{\"locations\":[{\"line\":1,\"column\":null}],\"message\":\"extraneous input '}' expecting {<EOF>, 'query', 'mutation', 'subscription', '{', 'fragment'}\"}]}}]}"

This is from re-graph to lacinia (rf/dispatch [::re-graph/query :handler-a "{hero {id name}}" {} [::on-result]])

the server-side was created with luminus

I can do the same query to a nodejs instance running graphql and it works fine

I guess what I am part. curious about is, where does this error message come from?