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
i found some docs on this kind "json select path" arg in the hasura docs. i'm not sure if this feature is a typical graphql pattern! so apologies if the above link is unnecessary
experimentation
from my testing, it seems that this particular field can be null when you search for a path that isn't found!
i changed the generated code to just be a "nullable string" for this field and everything worked. seems the jsonb decoder is just a Json.Decode.string. not sure the right API change in this case but thought this info could be useful!
i imagine this could be an error with the graphql server/schema itself rather than the elm-gql library? i'm not familiar enough with graphql client vs server to make that claim. i was under the impression that the schema was always correct, but i'm not sure!
The text was updated successfully, but these errors were encountered:
first off, incredible work!
relevant data to reproduce error
this example comes from the
https://pokeapi.co/
graphql apiquery:
elm-gql / elm-prefab config:
generated elm decoder:
relevant sprites field part of the schema (in case you didnt want to ping schema endpoint):
i found some docs on this kind "json select path" arg in the hasura docs. i'm not sure if this feature is a typical graphql pattern! so apologies if the above link is unnecessary
experimentation
from my testing, it seems that this particular field can be null when you search for a path that isn't found!
i changed the generated code to just be a "nullable string" for this field and everything worked. seems the
jsonb
decoder is just aJson.Decode.string
. not sure the right API change in this case but thought this info could be useful!i imagine this could be an error with the graphql server/schema itself rather than the elm-gql library? i'm not familiar enough with graphql client vs server to make that claim. i was under the impression that the schema was always correct, but i'm not sure!
The text was updated successfully, but these errors were encountered: