Dealing with namespaced keywords

[borkdude]

I'm trying to retrofit an existing REST endpoint (which returned EDN) to GraphQL using Lacinia.
The response contains a lot of namespaced keywords. Has Lacinia support for querying these?

[hlship]

Namespaces are a problem because the slash character is not allowed in a name (http://facebook.github.io/graphql/#sec-Names).

[bcarrell]

This is doable, but like @hlship mentioned, you'll need to find a way to map these keys in your data structure to keys in your GraphQL schema. My suggestion would be to override the default-field-resolver (see the default one here) to instead look up using whatever namespacing you're using.

Does that help?

EDIT: To elaborate, you could name your schema field name something like namespace__foo and then make your default-field-resolver fn passed to compile do something like if the field name has double underscores, look up in v using the namespaced keyword. Basically, you'll have to create a convention here since names can't have slashes.

[borkdude]

@bcarrell That's exactly what I've been doing as a workaround, the double underscores. Looks like it's more difficult to retrofit GraphQL on our backend, as we are using URIs as keys as well. I'll close this for now.