Repository navigation
Make search case insensitive #710
Description
Activity
I think it's one of those lose-lose situations. I will be very, very unhappy if I have to type in case sensitive type and method names every time I want to look something up related to Java, SJS, or Node.js. Or that "Connector" finds hits but "connector" doesn't.
If you're actively developing, do you really use your cell phone instead of your laptop to search the documentation? Let's be conscious of what use case we're optimizing for.
I think the right solution to this is an advanced search feature, not arbitrarily deciding that most searches would benefit from being case sensitive.
Well that was a dumb comment. I thought you were proposing to make the search case SENSITIVE. Sorry. Not enough morning tea ingested.
I still think the right answer is an advanced search control, but I won't throw a temper tantrum if you change it to case-insensitive. :)
There's a task out there somewhere for advanced search already, but you can guess how likely that is to happen in our lifetimes.
I think going case-insensitive by default, with an advanced feature for case-sensitive. And yes, advanced search isn't likely to happen soon.
From JH:
I agree with his reasoning -- the use of mobile devices changes the assumptions about capitalization.