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
You see: type: {value: "PERSON"} and type: {value: "ETHEREUM_ADDRESS"}
what is expected is type: PERSON and type: ETHEREUM_ADDRESS. This is straight up what the feature is supposed to do.
I'm using "json-to-graphql-query": "2.2.4"
The text was updated successfully, but these errors were encountered:
I'm having the same issue, running v2.2.5. I'm not sure if I'm meant to support this {value: ...} format on the API side, or if it's a problem with this library.
In the meantime, a workaround I've managed to implement is to add my problematic enum under __args rather than __variables. It means your enum will be hardcoded into the query itself rather than sent/validated as a variable.
File1:
file2:
Output:
You see:
type: {value: "PERSON"}
andtype: {value: "ETHEREUM_ADDRESS"}
what is expected is
type: PERSON
andtype: ETHEREUM_ADDRESS
. This is straight up what the feature is supposed to do.I'm using
"json-to-graphql-query": "2.2.4"
The text was updated successfully, but these errors were encountered: