False positives
hugomg opened this issue · 0 comments
hugomg commented
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.