If i have an interface like:

interface SomeInterface {
  id: ID! @isUnique
  users: [User!]! @relation(name: "SomeRelationOnUser")
  isPuplished: Bool! @defaultValue(value: false)
}

… and a type which implements this interface:

type SomeType implements SomeInterface {
  id: ID!
  users: [User!]!
  isPublished: Bool!
}

… should I repeat all those

@isUnique

,

@defaultValue

and

@relation

in the type declaration or it will be inherited from interface?

Interfaces are not supported yet with Graphcool

@agartha OK, thanks. Where can I see all the supported and unsupported features of GraphQL?

GraphQL is the specification. Graphcool is what you use to build your APIS with effortless. Being said this, this article explains what is GraphQL Schema Definition Language.

@jferrettiboke But you can see that every GraphQL type you use within Graphcool becomes

type YourTypeName implements Node

.

Node

is interface, so Graphcool is supporting interfaces at least internally. Where can I read which pieces of GraphQL specification are supported by Graphcool and which aren’t?

That’s correct. The only interface available is

Node

and is declared internally to take control about declaring the minimum fields on each

type

. At the moment,

id

field is the only obligatory field but a while ago

createdAt

and

updatedAt

were obligatory too.

@jferrettiboke Thank you very much for explanation. And one more question: are union types and enums supported by Graphcool?

I am not sure 100% but I think

union

is not supported.

There's full support for enum, not for

union

and

interface