2

I'm just playing with the new 2.0 API and in /tags there is a field inname that I can't find any description or documentation for.

What does it do? Is it like the old filter parameter on the old API?

Update: Now that I have the answer I've retagged this as a bug, meaning an omission from the documentation.

Improve this question

3 Answers 3

Reset to default
2

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

Improve this answer
2
  • No problem. It has a spelling mistake though: "The inname parameter let's a consumer filter down to tags that contain a certain substring". "Let's" is a contraction of "let us" - you should use plain "lets" here. Commented Dec 29, 2011 at 6:39
  • 1
    @hippietrail - typos will be fixed (there's on in /users too) with the next build. Commented Dec 29, 2011 at 7:41
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.

Improve this answer
2
  • Thanks. Should I tag this as "bug report" with the bug being an omission from the documentation? Commented Dec 28, 2011 at 17:50
  • Sure, that would be a good idea. Commented Dec 28, 2011 at 17:52
1

The inname parameter restricts the results of a name search to only those that contain the specified substring. The following methods support it:

filtering on badge, user, or tag names, as applicable.

Improve this answer

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.