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

"Fade" exact matches that are not the best module #97

Open
satazor opened this issue Sep 13, 2016 · 3 comments
Open

"Fade" exact matches that are not the best module #97

satazor opened this issue Sep 13, 2016 · 3 comments

Comments

@satazor
Copy link
Member

satazor commented Sep 13, 2016

Follow up of npms-io/npms-analyzer#63

Basically, if a exact match appears first but it's not the best module, it should be outlined somehow. We need to come with a good visual solution to make that clear.

@satazor satazor changed the title Highlight exact matches "Fade" exact matches that is not the best module Sep 16, 2016
@satazor
Copy link
Member Author

satazor commented Sep 20, 2016

An update: now you can specify boost-exact:false to disable this behavior.

@atduarte
Copy link
Member

We could add a tag like the "unstable" one, saying "exact match"

@satazor
Copy link
Member Author

satazor commented Sep 20, 2016

I think the flag by itself is not enough. The item should be less "visible" than others.

@satazor satazor changed the title "Fade" exact matches that is not the best module "Fade" exact matches that are not the best module Sep 21, 2016
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