SendToServer and complicate query

[felix-weizman-deel]

I'm trying to use Cashay and I have a problem with this query: { docs: allDocs{ edges{ node{ id, docUrl, fullUrl }} }

this is a post call to the server: {allDocs{ edges{} }}

This nodes didn't marked as sendToServer and they chopped off by minimizeQueryAST. Do you have any idea what may be the problem?

[mattkrick]

i'd have to see your schema to know what's up, but it looks like you're using a relay pattern. Is node an interface by chance? if so, it's probably related to #29 and I'd love for you to send me an example of what you're trying to do so I can build in interface functionality. I'm not opposed to it, I just can't think of an example to build into the test schema.

Also might be worth noting that Cashay was built to avoid the complexities of the edges, node paradigm. If you're using it by choice, that's totally valid, but if you're trying to accomplish something that can't be done any other way, drop me a line & i'll see if we can make it simpler.

[felix-weizman-deel]

Here is my schema.

We use Python for our backend with Graphene, and unfortunately it's the way it works.

[mattkrick]

nah, graphene doesn't have to be relay-enabled, does it? https://github.com/graphql-python/graphene/tree/master/examples/starwars

if you can adjust the test schema in a way so that a query or mutation returns an interface, i'd be glad to implement them, but since leaving the relay world i haven't had a need for interfaces & sometimes wonder if their sole purpose is for relay (I love being proved wrong though!).

[mattkrick]

@felix-zg should be fixed in v0.11.3, please re-open if not

[felix-weizman-deel]

Thanks!