-
Notifications
You must be signed in to change notification settings - Fork 3.2k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Discrepancy for JSON type between GraphiQL and API #3306
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
Comments
@martmull any idea for a quickfix on this since you've touched the console? Or does that seem like a more complex issue? |
@gitstart-twenty could you please look into this and see if you find a quick fix? Thanks |
Here is the GitStart Ticket for this issue: https://clients.gitstart.com/twenty/5449/tickets/TWNTY-3306 |
Hey @FelixMalfait It appears that GraphiQL has issues validating custom scalars in general and not just JSON. The errors however, do not affect the queries as they still work as expected. Please refer to the issues below for context:
There's also an RFC that proposes attaching a URI to custom scalars to provide a link to the scalar's definition here |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Uh oh!
There was an error while loading. Please reload this page.
GraphiQL (whether the docs version or the one on api.twenty.com) expects ECMA-404 formatting for JSON fields (i.e. a stringified JSON). But what the API expect is actually normal JSON (non sitringified).
In the screen below, the request was underlined as if it would fail but it turns out this request worked perfectly:
Query:
Variables:
The text was updated successfully, but these errors were encountered: