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

False positives #636

Open
hugomg opened this issue Aug 11, 2014 · 0 comments
Open

False positives #636

hugomg opened this issue Aug 11, 2014 · 0 comments

Comments

@hugomg
Copy link

hugomg commented Aug 11, 2014

Apparently, the filtering functionality includes a text search in the project's description, which can lead to false positives:. For example, when selecting "I need... a class system", around 25% of the libraries are erroneously listed just because they have "class" somewhere on their description:

  • chronoman (Utility class to...)
  • decisiontrees (classifier tag)
  • jvent (Event Emitter Class ...)
  • Router.js (... Home js class ....)
  • Transparency.js (has to do with CSS class attributes)
  • mediahack.js (media-query classes to DOM nodes)
  • Mouse (... mouse as a first class citizen)
  • ClassIE (the name is a coincidence)
  • atom.js (smal class providing...)
  • Corner.js (CSS classes again)

I understand that this filter might be specially affected because "class" is such an overloaded word but I wonder if there isn't a way to make the filter more accurate.

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