Share common fields between Input and Type in GraphQL

Question

I was wondering if there\'s a way to share the common fields between Input and Type in GraphQL so that I don\'t have to define the same set of fields in multiple places.

Answer 1

GraphQL fragments are for querying, not schema definition.

When I started learning GraphQL I was annoyed by this too because I was still thinking RESTfully. In most cases having the freedom to set certain fields non-nullable or remove them entirely from an input/output type is invaluable.

e.g.

input CreatePersonInput {
  name: String!
  slug: String
  address: String
}

type Person {
  id: ID! # Autogenerated on the server
  name: String!
  slug: String! # Will always exist, either user provided or computed
  # address: String # Omitted for security reasons
}

It may seem like a lot of extra code at first, but the flexibility this brings you over resource based schemas is worth it for long-term projects. I've seen it help out dozens of times.

You should also consider behavior/task-based mutations over resource or "anemic mutations"

I highly recommend learning about fat queries and read about Relay Specification. Even if you don't end up wanting Relay on the client, following some of their rules can really clear up common misconceptions about GraphQL.