I think a user would end up using variables for these things. So my query in code would look like
query findHotel($at: Point, $distance: Float) {
queryHotel(filter: {
location: {
near: {
coordinate: $at,
distance: $distance
}
}
}) {
name
}
}
Which seems pretty nice.
Definitely think we should only support what’s in Dgraph already. If any extra requirements come in. It’d probably have to be supported in Dgraph first, then bubbled into GraphQL.
One other thing I’d check is what sort of data structures do front end tooling that already does geo support - e.g. if there’s common JS libs in GraphQL for adding any of this to your app.
Also - Let’s move this to public so community can see