9

This seriously cripples any search capabilities.

Consider:

http://api.stackapps.com/0.8/search?intitle=soapi&order=desc&sort=activity vs

http://api.stackapps.com/0.8/search?intitle=Soapi&order=desc&sort=activity vs

http://api.stackapps.com/0.8/search?intitle=SOAPI&order=desc&sort=activity

This also begs the question "How many other textual parameters are case sensitive?"

it is my opinion that there should be no case sensitivity anywhere in the API.

Improve this question

2 Answers 2

Reset to default
4

Search intitle is now case insensitive.

Improve this answer
-2

I somewhat agree. I think that if there are case-sensitive parameters in the API, they should have some means by which they can be made case-insensitive.

What I think this should boil down to is the addition of a parameter like case-sensitive=true.

Improve this answer
2
  • Right, everyone would start using case-sensitive=false in their search. Commented Dec 6, 2010 at 3:44
  • @Gan: Well the default would be the opposite. Commented Dec 6, 2010 at 6:36

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.