Going back to the original issue...

So I have split up my schema into a number of seperate files, but now seem to have hit a circular dependency issue I can't resolve.

Basically I want to keep each query and mutation in a separate file.

So at the top-level I might have a schema like:

# schema.js
import { updateProject } from './mutations';
import { projectType } from './types';

const projectField = {
    type: projectType,
    description: 'Look up a project by ID or slug',
    .... 
};

const schema = new GraphQLSchema({
    query: new GraphQLObjectType({
        name: 'RootQueryType',
        description: 'The query root of GraphQL Interface',
        fields: () => ({
            project: projectField
        })
    }),
    mutation: new GraphQLObjectType({
        name: 'RootMutationType',
        fields: () => ({
            updateProject
        })
    })
});

With a projectType definition in a separate file

export const projectType = new GraphQLObjectType({
    name: 'Project',
    description: 'A project',
    fields: () => {
      name: {
        type: GraphQLString,
        description: 'Project',
        resolve: () => 'test'
      },
    }
});

Now suppose that my definition of updateProject is as follows

import { GraphQLNonNull, GraphQLInt, GraphQLString } from 'graphql';
import { projectType } from '../types';
import * as DB from 'db';

export default {
    type: projectType,
    args: {
      ...
    },
    resolve: (project, { }, request, info) => {
       ...
    }
};

When this setup is run, it will fall over with:

Error: Attribute.field field type must be Output Type but got: undefined.

So what happens is:

schema.js imports updateProject mutation
updateProject imports projectType
As this is not run-time, projectType.fields thunk has not been run, hence the error above.

It feels like I need a thunk on the type field of my mutation? Does anyone have any suggestions?

If a mutation or query has a type of something that uses a thunk for it's fields, then any field that uses it must also be inside a thunk? Seems impossible then to define it in a standalone file?

Schema circular dependency issue #373

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions