Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Case Sensitive Completion #11

Open
SeriousM opened this issue Feb 24, 2014 · 6 comments
Open

Case Sensitive Completion #11

SeriousM opened this issue Feb 24, 2014 · 6 comments

Comments

@SeriousM
Copy link

Hi, I really love this extension!
Just one thing bugs me: The selection is case sensitive.

When I have a function called getUserList I want to search for getuserlist and want to find it that way. Otherwise I have to 1. take care about how things are spelled and 2. may don't find what I'm searching for - especially with 3rd party libraries.

Could that become a setting or even default behaviour?

Thanks!

@MiguelCastillo
Copy link
Owner

@SeriousM I am glad you like the extension :)
I am thinking this could be a setting. I like the idea to have the flexibility to choose. Let me see what I can do.

@SeriousM
Copy link
Author

Thats awesome, thank you!

@SeriousM
Copy link
Author

Can I help you with that somehow?

@MiguelCastillo
Copy link
Owner

@SeriousM I have just changed ternific to allow case insensitive searches. I am still applying the logic to give highest priority to exact matches. So, if you are searching for hi and the there is hierarchy and Hi, hierarchy will be at the top simply because it matches casing. This is not in brackets registry yet, but you should be able to install it as a url. Let me know how it goes.

@SeriousM
Copy link
Author

wow, that looks good, thank you!

just one last question to this: do you also prioritize by typed length or just by case?
image

I would like to have both "resume" on top. what do you think?

@SeriousM
Copy link
Author

In addition to the example, what do you think about partial search? Like searching for "ume"...
Therefore someone could "explore" the api instead of scanning through every entry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants