`node` type should not be restricted to `ObjectType` about graphql-relay-js HOT 7 CLOSED

Hi, it makes sense to me not to restrict the node's type to ObjectType. Imagine I wanted to serve a list of mammals in a Connection, where some are dogs and some are cats. It makes sense in this case that my nodes are in InterfaceType and not an ObjectType. Without using InterfaceType as I've described, you have to create an ObjectType that bridges the functionality I want -- basically I create an ObjectType that has a field that is an InterfaceType that contains my mammal. It works, but it feels like a hack.

from graphql-relay-js.

Hm, I feel like you should be able to build connections to things other than object types; @yuzhi, thoughts?

from graphql-relay-js.

Relay currently does not support connection/pagination properly if the node is not an object. Relay does support List of objects or scalars. What's the specific use case?

from graphql-relay-js.

I think the main use-case is to be able to use interface and union types. Also the way it is defined now in the reference implementation implies that nodeType is always nullable. I wonder whether this is intentional?

My main motivation though is that I implemented the same kind of behaviour in sangria-relay previousely and in this particular place it contradicts the spec, so I get questions about it. People also ask whether it is possible to have an interface nodeType.

from graphql-relay-js.

@dwhitney Hi, I have a similar problem, and I tried the solution you proposed using an ObjectType that has a field that is an InterfaceType as my connectionType. However, I still couldn't get it to work.

Here is the error am getting:

"RelayQueryField: Range behavior keys are associated exclusively with connection fields. getRangeBehaviorKey() was called on the non-connection field %s."

Do you have any idea what I am missing? Thanks.

from graphql-relay-js.

just tested this client side, Relay (at least latest version) is happy with a connection of enums, and probably of interfaces too. I think the signature should change

from graphql-relay-js.

Fixed in #331

from graphql-relay-js.