[openstreetmap/openstreetmap-website] Supporting multiple API versions (#2353)

mmd notifications at github.com
Fri Aug 30 09:45:56 UTC 2019

>  I'm not intending to implement many changes, just the ones that I've been personally complaining about since API 0.6 was released over a decade ago (like incorrect http status codes, and plain-text responses, and stuff like that).

That's the bit I least like about the current multiple API version idea: it seems to focus on something I would describe as _cosmetic changes_ only. That's ok, except for it only adds work to consumers of the API while offering no real value to them at all. Since they already have a working API integration, they would need to spend extra development time and effort to get back to a status quo. 

Isn't there anything more compelling to do that would give API consumers more of an incentive to move to the latest and greatest version?

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/20190830/c7886c87/attachment.html>

More information about the rails-dev mailing list