Configuring the schema augmentation process

[michaeldgraham]

This PR contains initial support for configuring the schema augmentation process, resolving the following issues:

• How to disable generated mutations? How to disable generated mutations? #117
• Prevent auto generation of update, create, ... methods Prevent auto generation of update, create, ... methods #128

A config key is added to the makeAugmentedSchema argument object:

const augmentedSchema = makeAugmentedSchema({ 
  typeDefs,
  config: {
    query: true, // default
    mutation: false
  }
}

And the same configuration object is added as a second argument to augmentSchema:

const augmentedSchema = augmentSchema(schema, {
  mutation: false
});

By providing a boolean value, you can prevent the generation of the Query or Mutation API generally. For more fine-grained control, you can provide an array of type names to exclude (such as payload types, etc.) from the schema augmentation process. Excluding a type blocks the following associated API features from being generated during the schema augmentation process.

Query API

• A query for the excluded type is not generated.
• Any field or query that returns a list of the excluded type will not recieve first / offset / orderBy arguments.

Mutation API

• The create, update, and delete node mutations are not generated.
• The Add and Remove relation mutations are not generated for any relation in the schema coming from or going to excluded type.

Example

const config =  {
  query: {
    exclude: ["MyCustomPayload"]
  },
  mutation: {
    exclude: ["MyCustomPayload"]
  }
};
// const augmentedSchema = augmentSchema(schema, config);
const augmentedSchema = makeAugmentedSchema({ 
  typeDefs,
  config
}