Evaluate the interfaces field lazily (if defined as a thunk) about graphql-relay-js

[c0d0g3n]

@kamek-pf and all others that stumble upon this issue: You can now define interfaces as a thunk. It worked for me (using [email protected] and [email protected]) and swapi-graphql is using it too.

Hope this saves some people some searching :)

[dschafer]

@leebyron, thoughts? This would probably be a change to https://github.com/graphql/graphql-js

[wincent]

The thunk idea sounds reasonable on the surface.

As a workaround in the meantime @kamek-pf, you have a couple of options. One is just keeping everything that implements the interface in a single file (not great, obviously). The other: in a side project I ended up using a registration pattern to avoid the circular dependency issues.

[kevinSuttle]

I think this is something that GraphQL-JS needs to address. I got stuck on a circular dependency the very first time I tried to implement an Interface. Perhaps it's a doc issue? There is currently very little documentation, and what's there is super confusing.

https://facebook.github.io/graphql/#sec-Interface-type-validation

The fields of an Interface type must have unique names within that Interface type; no two fields may share the same name.

Uh?

[kevinSuttle]

@leebyron Would love to hear your thoughts on this, because it's both a GraphQL and a JavaScript issue, meaning, as soon as you try to circumvent the circular dependency by putting import statements into your resolveType: function, you get a syntax error in ES6. Using require then throws weird errors about outputType if you've followed the SWAPI implementation.