You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Larger 64 bit integers get truncated in Altair.
To Reproduce
I think this should be reproducible with any GraphQL API that returns 64 bit integers (larger than a certain value) in extensions section.
Expected behavior
The integer should be rendered as returned by the API.
Screenshots
The number underlined in RED gets rendered as 3902760572613809000. However, the API actually returns 3902760572613809272.
Desktop (please complete the following information):
OS: Windows
Additional context
I think this behavior has something to do with the GraphQL spec that does not support 64 bit integers. But I think the current behavior is a little misleading as it silently truncates the numbers (even in extensions section of the response). Can we start supporting 64 bit integers in Altair?
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
Larger 64 bit integers get truncated in Altair.
To Reproduce
I think this should be reproducible with any GraphQL API that returns 64 bit integers (larger than a certain value) in
extensions
section.Expected behavior
The integer should be rendered as returned by the API.
Screenshots

The number underlined in RED gets rendered as
3902760572613809000
. However, the API actually returns3902760572613809272
.Desktop (please complete the following information):
Additional context
I think this behavior has something to do with the GraphQL spec that does not support 64 bit integers. But I think the current behavior is a little misleading as it silently truncates the numbers (even in
extensions
section of the response). Can we start supporting 64 bit integers in Altair?The text was updated successfully, but these errors were encountered: