Geometry Scalar should expect a WKT or a Geometry Object.

[olmohake]

Component

c/v3-engine

Is your proposal related to a problem?

At the moment it's necessary to stringify the geometry object.

query find($Geometry:Geometry!){
   postcode(where:{geometry:{st_contains:$Geometry}}){
      number
   }
}

{
  "Geometry": "{\"type\":\"Point\",\"coordinates\":[391968,5818620],\"crs\":{\"type\":\"name\",\"properties\":{\"name\":\"EPSG:25833\"}}}"
}

Describe the solution you'd like

Geometry should be a Object instead of a Scalar. This would not only align with the way geometry inputs work but also enable the graphql engine and ui tools like houdini to check the validity of the input in advance. i.e. disallow geometries with an invalid type property.

query find($Geometry:Geometry!){
   postcode(where:{geometry:{st_contains:$Geometry}}){
      number
   }
}

{
  "Geometry": {
    "type": "Point",
    "coordinates": [
      391968,
      5818620
    ],
    "crs": {
      "type": "name",
      "properties": {
        "name": "EPSG:25833"
      }
    }
  }
}

Describe alternatives you've considered

[robertjdominguez]

Thanks, @olmohake 👍

I've tagged the team responsible for this.

[olmohake]

Thanks! Just realised turning the Geometry type itself from Scalar to Object, might create other problems down the road as you'd loose support for WKT formatted geometries.

Best way forward would probably be to keep the Scalar and enable users to pass in a Geometry Object or WKT formatted Geometries.

I adjusted the title of the issue accordingly.