Tag Info

It is supposed to include answers (probably first page only), and documented (look for "answers" in return json), but there was a bug, and it has been fixed recently. But yes, I also think answer=true option would be nice.

We're using number in the JSON sense of the word. number in that context does cover all the data types we're returning. I suppose it could be tightened up a bit, though... Descriptions of the types of number coming back are now part of the /help docs.

It would make more sense - in my opinion - for a library to abstract the paged nature of results away entirely. Furthermore, there's no need for the objects exposed by whatever deserialization code to reflect the naming scheme of the underlying JSON. If you want more automatic code, you could just define the data field as not total, page, or pagesize. The ...

"Vectorized" does not imply anything about the order of its constituent components. The name comes from Vector Processors, a nicer name for the SIMD scheme. The parameters are all treated identically, the documentation for each will be brought into sync on the next code push.

Hmmm. Currently {tags} is a space delimited set of tag names. It really ought to be a semicolon delimited set. So, the next code push will switch to the semicolon behavior. The documentation will be updated to reflect this. This code has been deployed now.