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
Description
When using schema stitching to send requests to a remote resource number variables are not given a trailing comma, therefore producing invalid json.
I've experimented with this and it seems if the remote schema is hotchocolate it will happily parse this invalid json, but other gql implementations won't.
To Reproduce
Set up schema stitching to consume a remote schema.
make a query of the remote schema using one or more number variables (issue exists for ints and floats).
Inspect the body of the http request made - note that number variables are not followed by commas, as they should per json spec.
Expected behavior
valid Json produced.
Additional context
I've put together a fix for this and a test describing the problem. I'll submit a PR
The text was updated successfully, but these errors were encountered:
Description
When using schema stitching to send requests to a remote resource number variables are not given a trailing comma, therefore producing invalid json.
I've experimented with this and it seems if the remote schema is hotchocolate it will happily parse this invalid json, but other gql implementations won't.
To Reproduce
Expected behavior
valid Json produced.
Additional context
I've put together a fix for this and a test describing the problem. I'll submit a PR
The text was updated successfully, but these errors were encountered: