Invalid schema generated when a related list has access: false

[timleslie]

When a list has a relationship to another list with access: false, keystone generates an invalid graphQL schema.

keystone.createList('User', {
  fields: {
    name: { type: Text },
    post: { type: Relationship, ref: 'Post', many: false },
  },
  access: true,
});

keystone.createList('Post', {
  fields: {
    name: { type: Text },
  },
  access: false,
});

Error: Unknown type "PostWhereUniqueInput". Did you mean "UserWhereUniqueInput", "PostRelateToOneInput", "UserWhereInput", "UserUpdateInput", or "UsersUpdateInput"?

While this is a fairly obscure access control configuration, it's something that can come up in systems which support multiple different schemas.

The solution involves checking for refList.access[schemaName] in the Relationship methods getGqlAuxTypes, gqlUpdateInputFields, and gqlCreateInputFields. Unfortunately the latter 2 of these are getter functions, so we can't pass in schemaName as required. Fixing the issue will require us to change these getter functions and pass in { schemaName }.