Skip to content

Custom type does not exist for Hasura Action #8655

Discussion options

You must be logged in to vote

Hello @kevinmichaelchen,

Maybe a little bit late, but the solution is to use input nesting in your case.

input LatLng {
  lat: Float!
  lng: Float!
}

input DistanceMatrixInput {
  origins: [LatLng]
  destinations: [LatLng]
}

And of course, don't forget to declare LatLng as an input in your actions.yaml.

Cheers.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by kevinmichaelchen
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants