Skip to content

64 bit integers #295

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Coolaswa opened this issue Feb 16, 2022 · 2 comments
Closed

64 bit integers #295

Coolaswa opened this issue Feb 16, 2022 · 2 comments
Labels
type: question or discussion Issue discussing or asking a question about gql

Comments

@Coolaswa
Copy link

I am interfacing with the graphQL API of monday.com. Their item IDs have recently passed 2^31 and when I request such an item gql trows an error:

Int cannot represent non 32-bit signed integer value: 2300634791

GraphQL request:2:18
1 | {
2 |     boards (ids: 2300634791) {
  |                  ^
3 |     items(limit:1000){

monday.com have a handy API tester where I can input my query directly, and the response comes back without issue, thus leading me to believe the issue is with gql. Now, I know of this issue in the graphQL spec: graphql/graphql-spec#73, but I am not sure it is relevant here.

To Reproduce
Steps to reproduce the behavior:
To interface with monday.com you need API authorization so I'm not sure I can provide this. But I assume trying to query a graphQL Int larger than 2^31 will reproduce this error.

Expected behavior
Since the monday.com API playground gives normal results I would expect the same result from gql.

System info:

  • OS: Windows 10
  • Python version: 3.9.9
  • gql version: 3.0.0
  • graphql-core version: 3.2.0

Thanks in advance for any help

@leszekhanusz
Copy link
Collaborator

Could you please download the schema with your credentials to show the type of ids?

Does it work correctly if you don't have a local schema (set fetch_schema_from_transport to False) ?

@leszekhanusz leszekhanusz added type: question or discussion Issue discussing or asking a question about gql status: waiting for author The PR author should address requested changes labels Feb 18, 2022
@Coolaswa
Copy link
Author

Hi, thanks for your response.
I have implemented your proposal and it seems to fix the issue I was having. Many thanks!

@leszekhanusz leszekhanusz removed the status: waiting for author The PR author should address requested changes label Feb 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: question or discussion Issue discussing or asking a question about gql
Projects
None yet
Development

No branches or pull requests

2 participants