You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: