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

ui: Improve autocompletion #1924

Open
beorn7 opened this Issue Aug 26, 2016 · 2 comments

Comments

Projects
None yet
4 participants
@beorn7
Copy link
Member

beorn7 commented Aug 26, 2016

We had iterated quite a bit on autocompletion in the expression browser, see #907 and #1181 . However, we reverted them all in #1303 because of the problems reported in #1185 . We never came back to it, but we should. Problem so far was that nobody felt really qualified about those UI intricacies.

@davkal (who asked for this issue).

@biglovisa

This comment has been minimized.

Copy link
Contributor

biglovisa commented Dec 5, 2017

Is this related to #3187, improving the matching algorithm for the expression browser? I was just touching that code and was hoping to find some time to take a look at it.

@davkal

This comment has been minimized.

Copy link
Contributor

davkal commented Dec 5, 2017

At the minimum, I believe this issue was to make the suggester work mid-query, not just at the beginning, e.g., for queries like go_gc_duration_seconds + go, where you dont get suggestions for the second go prefix. #3187 is more about the weighting (or lack thereof) in the fuzzy matching algorithm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.