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
Dealing with a 馃う API, some endpoints seem to require that for some queries, the id be an Integer, but for others, a String. I know that for providing our own mutation variables, it's possible to make explicit whether we want a string or int (like "\"123\""), but it seems there's no way to do that for a computed variable. Any thoughts on how that could be accomplished? I keep getting back an id of "123", but when providing it to the endpoint, it gets recognized as JSON and converted to 123.
The text was updated successfully, but these errors were encountered:
Dealing with a 馃う API, some endpoints seem to require that for some queries, the
id
be anInteger
, but for others, aString
. I know that for providing our own mutation variables, it's possible to make explicit whether we want a string or int (like"\"123\""
), but it seems there's no way to do that for a computed variable. Any thoughts on how that could be accomplished? I keep getting back an id of"123"
, but when providing it to the endpoint, it gets recognized as JSON and converted to123
.The text was updated successfully, but these errors were encountered: