我目前正在尝试继承rootQuery的模式以获得更多的模块化。设置目前如下所示:
invoiceSchema.js
import {
GraphQLObjectType,
GraphQLInt,
} from 'graphql';
export default new GraphQLObjectType({
name: 'Invoice',
description: 'A monthly billing invoice for an organization',
fields: () => ({
amountDue: {
type: GraphQLInt,
description: 'The amount the card will be charged (total + startingBalance with a min value of 0)'
},
})
});
rootQuery.js
import {
GraphQLObjectType,
GraphQLString,
GraphQLInt,
GraphQLList,
GraphQLID
} from 'graphql';
import Invoice from './invoiceSchema';
export default {
Invoice: {
type: Invoice,
resolve(parentValue, args){
return 'Hello world';
}
}
};
schema.js
import query from './rootQuery';
import {GraphQLSchema} from 'graphql';
export default new GraphQLSchema({query});
当尝试执行以下错误并希望得到一些帮助和见解时,因为我在invoiceSchema.js中导出的内容显然是ObjectType而不是对象Object。
C:\project\node_modules\graphql\jsutils\invariant.js:19
throw new Error(message);
^
Error: Schema query must be Object Type but got: [object Object].
at invariant (C:\project\node_modules\graphql\jsutils\invariant.js:19:11)
at new GraphQLSchema (C:\project\node_modules\graphql\type\schema.js:72:88)
at Object.<anonymous> (C:/project/api/schema/schema.js:6:16)
at Module._compile (module.js:573:30)
at loader (C:\project\node_modules\babel-register\lib\node.js:144:5)
at Object.require.extensions.(anonymous function) [as .js] (C:\project\node_modules\babel-register\lib\node.js:154:7)
at Module.load (module.js:507:32)
at tryModuleLoad (module.js:470:12)
at Function.Module._load (module.js:462:3)
at Module.require (module.js:517:17)
[nodemon] app crashed - waiting for file changes before starting...
实际上从here得到了这个想法,我想知道为什么它不起作用......
答案 0 :(得分:3)
您的根查询需要是GraphQLObjectType
的实例,但rootQuery.js
正在导出普通的Object。您需要将导出更改为以下内容:
export default new GraphQLObjectType({
name: 'RootQuery',
fields: () => ({
invoice: {
type: Invoice,
resolve(parentValue, args){
return 'Hello world';
}
}
})
};
注意:通常的做法是将所有字段名称(包括查询和变异名称)保存在camelCase中,并使用PascalCase作为类型名称,以帮助区分这两者。
此外,如果您要模块化模式,您可能会发现使用graphql-tools
来生成模式会很有帮助。 IMO,它使您的架构更具可读性,并有助于避免在模块化模式时可能遇到的一些更常见的陷阱。这些文档提供了一个很好的示例,说明如何使用makeExecutableSchema
here模块化您的架构。