graphql-js

问题 If I have an object: {"where":{"publishedAt_lt":"2018-01-01"}} How can I convert it to a string suitable for query arguments? articles(where: {publishedAt_lt: "2018-01-01"}) 回答1: This looks like an interesting library, I would suggest checking it out: https://www.npmjs.com/package/json-to-graphql-query But basically all we need to do is to convert the object to a string while ensuring the keys do not adopt double quotes and integers are not converted into strings, as that might not play well

来源： https://stackoverflow.com/questions/39504986/document-a-graphql-api

来源： https://stackoverflow.com/questions/39504986/document-a-graphql-api

问题 I am using apollo-server and apollo-graphql-tools and I have following schema type TotalVehicleResponse { totalCars: Int totalTrucks: Int } type RootQuery { getTotalVehicals(color: String): TotalVehicleResponse } schema { query: RootQuery } and Resolver functions are like this { RootQuery: { getTotalVehicals: async (root, args, context) => { // args = {color: 'something'} return {}; }, TotalVehicleResponse: { totalCars: async (root, args, conext) => { // args is empty({}) here ......... .....

问题 I have some object types that I'd like to use as both input and output - for instance a currency type or a reservation type. How do I define my schema to have a type that supports both input and output - I don't want to duplicate code if I don't have to. I'd also prefer not to create duplicate input types of things like currency and status enums. export const ReservationInputType = new InputObjectType({ name: 'Reservation', fields: { hotelId: { type: IntType }, rooms: { type: new List

问题 I have some object types that I'd like to use as both input and output - for instance a currency type or a reservation type. How do I define my schema to have a type that supports both input and output - I don't want to duplicate code if I don't have to. I'd also prefer not to create duplicate input types of things like currency and status enums. export const ReservationInputType = new InputObjectType({ name: 'Reservation', fields: { hotelId: { type: IntType }, rooms: { type: new List

问题 I have some object types that I'd like to use as both input and output - for instance a currency type or a reservation type. How do I define my schema to have a type that supports both input and output - I don't want to duplicate code if I don't have to. I'd also prefer not to create duplicate input types of things like currency and status enums. export const ReservationInputType = new InputObjectType({ name: 'Reservation', fields: { hotelId: { type: IntType }, rooms: { type: new List

问题 I developed a graphql node js app with custom resolvers. Can anyone point me to some documentation where it illustrates how to properly write unit tests for my service? Or if someone has done it before and can point me in the right direction that would be great! 回答1: In order to test each endpoint of your service, you need to perform a POST operation on specified URL with proper payload. The payload should be an object containing three attributes query - this is a GraphQL query that will be

问题 I'm using apollo client for graphql. I set up the client in AppApolloModule that I'm importing in AppModule. I'm making a query in a service which is also imported right in the AppModule. Although the service runs before the AppApolloModule runs and hence apollo is not initialized when the query is made and I get this error Error: Client has not been defined yet AppApolloModule imports .... export class AppApolloModule { constructor( apollo: Apollo, httpLink: HttpLink, private userService:

问题 In an express-graphql app, I have a userLogin resolver like so: const userLogin = async ({ id, password }), context, info) => { if (!id) { throw new Error('No id provided.') } if (!password) { throw new Error('No password provided.') } // actual resolver logic here // … } If the user doesn't provide an id AND a password , it will throw only one error. { "errors": [ { "message": "No id provided.", "locations": [ { "line": 2, "column": 3 } ], "path": [ "userLogin" ] } ], "data": { "userLogin":