4 ms·
This is great! One quick feedback, you should probably normalize the case in searches. I searched for "python" and got nothing. I had to change it to "Python
by jedberg 11y ago
This is great!
One quick feedback, you should probably normalize the case in searches. I searched for "python" and got nothing. I had to change it to "Python" to get it to work.
- decentrality 11y agoI noticed this immediately too. But since there are a fixed set of possible languages, seems like a dropdown box and/or multi-select would do the trick and remove the possibility of user error.
- muricula 11y agoWe use the language reported by the GitHub api, so the list of languages may change without notice. We should definitely normalize capitalization and I think there are node libraries edit distance we could leverage too. Thanks for the advice!
- nanny 11y agoI'd like to be able to search "lisp" and get both Common Lisp and Emacs Lisp. I tried that and was surprised when nothing showed up.
- Zikes 11y agoI think that would be best handled by manually coding a set of language synonyms, rather than substring searches. Shorter language names could cause problems in the latter, such as C and Go.