Tell me more ×
Stack Apps is a question and answer site for apps, scripts, and development with the Stack Exchange API. It's 100% free, no registration required.
up vote 1 down vote favorite

I realize that the API is frozen, hence tagging this as support rather than feature-request or bug - I'm irritated about the two routes /badges/name and /badges/tags:

  • They seem to simply filter down what's available via /badges anyway? Aside from the option to filter /badges client side via a lookup for "tag_based" (as argued/suggested by Kevin for another case), the API is using query parameters rather than paths elsewhere for (simple) filter operations on a resource collection like this (and correctly so, from a RESTful perspective).
  • Even if desired, 'name' is singular were 'tags' is plural, which seems odd to me (might as well be a non native speaker issue though ;)

Has this asymmetric design been chosen deliberately and are there any insights into the decision available in case? Am I missing a use case one should know about when using these routes?

share|improve this question
i think is is vestigal. – Sky Sanders Jul 25 '10 at 12:55
@code poet - LOL, I actually had to look that word up and have been confused for a second by the picture illustrating the most common example in the context of the human body ;) Your evolution analogy seems to be more prevalent within API 1.0 than I'd hoped for even from an agile POV - well, it's basically working fine, but given the lack of time frame regarding 2.0 or any 1.x versions I've already started to think about artificial mutations to compensate this, though this might be a risky effort ... – Steffen Opel Jul 25 '10 at 15:20

You must log in to answer this question.

Browse other questions tagged