Text search doesn't match (@usernames)

[aseemk]

One more quick issue: our <option> elements' text looks like "Aseem Kishore (@aseemk)". If I search for "aseem" or "kishore", it matches those parts of the string, but if I type in "aseemk" or "@aseemk", it doesn't work.

What do you guys think? Sound like a reasonable thing to support?

[pfiller]

Chosen doesn't skip parentheses when searching yet (see issue #206). #387 would help you skip the @ sign. Hopefully we can get a bunch of these pull requests handled this week.

[aseemk]

Thanks for the parentheses reference.

Would it be necessary for us to specify that @ should be skipped? Would "aseemk" not match "@aseemk"?

[pfiller]

If the @ symbol was not put in the skip array, the regex would only match @asseemk precisely because it starts at the beginning of strings.

[aseemk]

So it wouldn't be possible to match both aseemk and @aseemk in this list? =/

[pfiller]

If we applied the replacement to the search string as well as the option, they would match. Right now, it's just applied to the option, so we'll have to take a look at that. Feel free to offer some code solution that handles this case.