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
Passing in { "id": 1 } to the api throws -> "runtime error: slice bounds out of range [1:0]"
As you can clearly see, I am sure I have issues but Wundergraph just doesn't get them.
This only happens with a single digit like 1, however it returns a null value when a multiple digit value is given like 10, even if a record with that ID exists in the database.
The first error can be resolved with this fix: #697. However it doesn't seem to be the root cause, the graph-go-tools repo is a bit dense for me to parse through but I think the BigInt value is getting incorrectly resolved to a string in the request.
I can work around this by replacing the BigInt with db_IssueWhereUniqueInput,
Given this simple query for my issues:
Passing in { "id": 1 } to the api throws -> "runtime error: slice bounds out of range [1:0]"
As you can clearly see, I am sure I have issues but Wundergraph just doesn't get them.
This only happens with a single digit like
1
, however it returns a null value when a multiple digit value is given like10
, even if a record with that ID exists in the database.The first error can be resolved with this fix: #697. However it doesn't seem to be the root cause, the graph-go-tools repo is a bit dense for me to parse through but I think the BigInt value is getting incorrectly resolved to a string in the request.
I can work around this by replacing the
BigInt
withdb_IssueWhereUniqueInput
,And thankfully when I do this I can see that my issues are right where I left them.
Pasting the full stack trace below:
The text was updated successfully, but these errors were encountered: