Tag Info

Hot answers tagged

3

Are they moved to filters? Yes, you need to generate a filter that includes the question.body, question.comments, and question.answers fields. There are shorthand filters (i.e. _bca) that will do this for upgrade compatibility, but their use is discouraged and you're better off just making a filter that contains exactly what you want anyway.


2

inname has been documented on /users and /tags now. Thanks for catching that oversight.


2

body and comments have been removed from those methods.


1

The inname parameter restricts the results of a name search to only those that contain the specified substring. The following methods support it: /badges /badges/name /badges/tags /users /tags /tags/required /tags/moderator-only filtering on badge, user, or tag names, as applicable.


1

inname limits the returned items to only those that contain the specified value. This parameter is identical to the filter parameter in v1.0 and v1.1 of the API. Note: this parameter is also present in the /users route.


1

todate and fromdate always refer to creation date. min and max are with respect to the current sort. So, where sort=votes they place upper and lower bounds on the score of returned answers/questions. They can overlap, but do not always do so. Documentation has been updated to reflect that min and max can be of any number of types. /search for example. ...


1

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.



Only top voted, non community-wiki answers of a minimum length are eligible