starred/gql-query-builder

Fork 0

mirror of https://github.com/atulmy/gql-query-builder.git synced 2026-04-25 23:55:55 +03:00

[GH-ISSUE #45] Add enum #117

New issue

Open

opened 2026-03-15 11:33:09 +03:00 by kerem · 6 comments

kerem commented

2026-03-15 11:33:09 +03:00

Owner

Originally created by @felipe-gustavo on GitHub (Jul 3, 2020).
Original GitHub issue: https://github.com/atulmy/gql-query-builder/issues/45

i have some query that need add Enum like that:

{
  diagnostic__defects(page: 1, orderBy: [{field: IS_FUNCTIONAL_DEFECT, order: DESC}]) {
    data {
      id
      name
    }
  }
}

IS_FUNCTIONAL_DEFECT and DESC are ENUM, can't be wrapped by quote

Originally created by @felipe-gustavo on GitHub (Jul 3, 2020). Original GitHub issue: https://github.com/atulmy/gql-query-builder/issues/45 i have some query that need add Enum like that: ```GraphQL { diagnostic__defects(page: 1, orderBy: [{field: IS_FUNCTIONAL_DEFECT, order: DESC}]) { data { id name } } } ``` IS_FUNCTIONAL_DEFECT and DESC are ENUM, can't be wrapped by quote

kerem added the

help wanted

label

2026-03-15 11:33:09 +03:00

kerem commented

2026-03-15 11:33:20 +03:00

Author

Owner

@atulmy commented on GitHub (Jul 4, 2020):

@felipe-gustavo feel free to open a PR for this use case.

@atulmy commented on GitHub (Jul 4, 2020): @felipe-gustavo feel free to open a PR for this use case.

kerem commented

2026-03-15 11:33:25 +03:00

Author

Owner

@Devorein commented on GitHub (Jul 5, 2020):

@felipe-gustavo can you try the following command

const gqlquery = query([
  {
    operation: "diagnostic__defects",
    variables: {
      page: {
        value: 1
      },
      orderBy:{
        list: true,
        type: 'type your order input value here, defined in the schema',
        value: {field: 'IS_FUNCTIONAL_DEFECT', order: 'DESC'}
      }
    },
    fields: [{'data':['id','name']}]
  },
]);

@Devorein commented on GitHub (Jul 5, 2020): @felipe-gustavo can you try the following command ```js const gqlquery = query([ { operation: "diagnostic__defects", variables: { page: { value: 1 }, orderBy:{ list: true, type: 'type your order input value here, defined in the schema', value: {field: 'IS_FUNCTIONAL_DEFECT', order: 'DESC'} } }, fields: [{'data':['id','name']}] }, ]); ```

kerem commented

2026-03-15 11:33:30 +03:00

Author

Owner

@Devorein commented on GitHub (Jul 5, 2020):

@felipe-gustavo Atm there is no way to embed argument values directly, but hopefully the above will work, otherwise I'll send a PR to embed argument values directly without using variables

@Devorein commented on GitHub (Jul 5, 2020): @felipe-gustavo Atm there is no way to embed argument values directly, but hopefully the above will work, otherwise I'll send a PR to embed argument values directly without using variables

kerem commented

2026-03-15 11:33:35 +03:00

Author

Owner

@ehrenmurdick commented on GitHub (Nov 11, 2021):

@Devorein @atulmy I have the same use case. The above command you posted did not work for me. Has there been any update on this?

@ehrenmurdick commented on GitHub (Nov 11, 2021): @Devorein @atulmy I have the same use case. The above command you posted did not work for me. Has there been any update on this?

kerem commented

2026-03-15 11:33:40 +03:00

Author

Owner

@julienlagorsse-loreal commented on GitHub (Jan 31, 2023):

Same here.

@julienlagorsse-loreal commented on GitHub (Jan 31, 2023): Same here.

kerem commented

2026-03-15 11:33:45 +03:00

Author

Owner

@ehrenmurdick commented on GitHub (Feb 2, 2023):

To spare the sanity of anyone else who might resort to reading the graphql spec like me, no the graphql spec doesn't say that the server must accept strings in the variables transport for enum values. It specifically says it may accept strings. The relevant section is here: https://spec.graphql.org/October2021/#sec-Enums.Input-Coercion

I think I have enough time today to implement a PR for this so I'm working on it now.

@ehrenmurdick commented on GitHub (Feb 2, 2023): To spare the sanity of anyone else who might resort to reading the graphql spec like me, no the graphql spec doesn't say that the server *must* accept strings in the variables transport for enum values. It specifically says it *may* accept strings. The relevant section is here: https://spec.graphql.org/October2021/#sec-Enums.Input-Coercion I think I have enough time today to implement a PR for this so I'm working on it now.