[openstreetmap/openstreetmap-website] Plans for GraphQL support? (#2047)

Jason Sun notifications at github.com
Fri Nov 9 23:50:07 UTC 2018

@mmd-osm I think "what kind of simplification" isn't the right question, because GraphQL would be unifying all the different endpoints into a single URL and all the CRUD functions would be preserved -- so there is no simplification as to what the functionalities are.

As to "which use cases those would be relevant", I was looking to make use of OSM backend as part of my mapping infrastructure with my own data set. I am considering to write a custom frontend that consumes a select portion of that. It would've been easier to consume GraphQL because of its contractual basis, so I wouldn't need to hunt around for the data I needed.

@tomhughes you wouldn't need to coordinate existing clients with a different API. Effectively we'd open up a single new endpoint for handling GraphQL features, and anyone who wants to make use of that can do so. It's common to have a GraphQL layer to bridge existing services, essentially providing a translation service to existing APIs.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20181109/48ebd1ba/attachment.html>

More information about the rails-dev mailing list