[openstreetmap/openstreetmap-website] API for user blocks (#1618)

[Simon Poole]

@gravitystorm osmcha and probably every other use case that needs to access any user information already hits the user endpoint (at least once), example http://api.openstreetmap.org/api/0.6/user/100950 I suspect referring to a dump of the data (which currently doesn't exist) is not going to be very popular (not to mention premature optimisation etc).

Even if my suggestion of simply adding a last block attribute is considered too hackish, a -separate- API doesn't seem to make sense when additional information can simply be added to the already existing blocks section in the user API (even in the worst case we are not talking about more than a handful of entries).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/1618#issuecomment-325188199
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20170827/57e62ae2/attachment.html>