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
I'm not sure about hard-coding patterns for classnames like these into the library itself. Seems to me that it could lead to unforeseen false-positives. Maybe I could put together some examples of blacklists for specific libraries and list them in the Readme, to make it easy for users of this library to use them at their own risk. What do you think?
Yes, add a callback to determine whether a class / id should be used in a selector. The user can use the method that suits best for him. For example detecting the entropy of the string, or using a whitelist, a regex, or any other method
With more and more websites using CSS modules,
css-selector-generator
often generates fickle selectors that are only valid until the next deployment.Would it be possible to automatically detect and exclude these selectors, optionally?
The text was updated successfully, but these errors were encountered: