[GH-ISSUE #12] support for primitive return types? #4

New issue

Closed

opened 2026-03-03 00:02:40 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 00:02:40 +03:00

Owner

Originally created by @albertalquisola on GitHub (May 27, 2019).
Original GitHub issue: https://github.com/atulmy/gql-query-builder/issues/12

Originally assigned to: @atulmy on GitHub.

it seems the builder expects an object to always be returned in a graphql response since the fields arg is required. But what if the graphql server responds with a primitive? (eg. GraphQLBoolean)

Example:

// mutation portion of schema
new GraphQLObjectType({
  name: 'RootMutation',
  fields: { 
    logout: {
      type: GraphQLBoolean,
      resolve: async () => await pretendToLogUserOut(), // returns boolean
    }
  }
});

// query
import { mutation } from 'gql-query-builder';

const logoutMutation = mutation({ operation: 'logout', fields: [] });
console.log(logoutMutation.query);

// query output
mutation {
  logout {
    // this causes a 400 since i dont list any fields but that's because the response doesnt return `fields`, it just returns a bool
  }
}

// desired query output
mutation {
  logout
}

The result is a 400 since this is a malformed query string so it seems the query builder does not have support for handling primitive return values?

Originally created by @albertalquisola on GitHub (May 27, 2019). Original GitHub issue: https://github.com/atulmy/gql-query-builder/issues/12 Originally assigned to: @atulmy on GitHub. it seems the builder expects an object to always be returned in a graphql response since the `fields` arg is required. But what if the graphql server responds with a primitive? (eg. GraphQLBoolean) Example: ``` // mutation portion of schema new GraphQLObjectType({ name: 'RootMutation', fields: { logout: { type: GraphQLBoolean, resolve: async () => await pretendToLogUserOut(), // returns boolean } } }); ``` ``` // query import { mutation } from 'gql-query-builder'; const logoutMutation = mutation({ operation: 'logout', fields: [] }); console.log(logoutMutation.query); ``` ``` // query output mutation { logout { // this causes a 400 since i dont list any fields but that's because the response doesnt return `fields`, it just returns a bool } } // desired query output mutation { logout } ``` The result is a 400 since this is a malformed query string so it seems the query builder does not have support for handling primitive return values?

kerem

2026-03-03 00:02:40 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-03 00:02:41 +03:00

Author

Owner

@atulmy commented on GitHub (May 28, 2019):

Check: https://github.com/atulmy/gql-query-builder/issues/8#issuecomment-481789433

@atulmy commented on GitHub (May 28, 2019): Check: https://github.com/atulmy/gql-query-builder/issues/8#issuecomment-481789433

kerem commented

2026-03-03 00:02:41 +03:00

Author

Owner

@albertalquisola commented on GitHub (May 28, 2019):

I'm unsure how this addresses the issue? I dont need to specify a custom variable type (i dont think), I need my query output to not always expect an object being returned

@albertalquisola commented on GitHub (May 28, 2019): I'm unsure how this addresses the issue? I dont need to specify a custom variable type (i dont think), I need my query output to not always expect an object being returned

kerem commented

2026-03-03 00:02:41 +03:00

Author

Owner

@atulmy commented on GitHub (May 28, 2019):

Sorry got it, you want the fields to be optional

@atulmy commented on GitHub (May 28, 2019): Sorry got it, you want the `fields` to be optional ![Screenshot 2019-05-29 at 12 15 04 AM](https://user-images.githubusercontent.com/685786/58503762-de8f5380-81a6-11e9-84ef-da312df40189.png)

kerem referenced this issue

2026-03-03 00:03:06 +03:00

[PR #6] Generalize API #63

kerem referenced this issue

2026-03-03 00:03:16 +03:00

[PR #31] [MERGED] Fix undefined variable - Resolved #23 #74

kerem referenced this issue

2026-03-15 11:27:53 +03:00

[GH-ISSUE #4] Single query, multiple operations #96

kerem referenced this issue

2026-03-15 11:37:58 +03:00

[PR #6] [MERGED] Generalize API #142