We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Would be cool addition to include CSS specificity into the metrics provided.
Specificity is great as it gives you information about what your rules are actually made up of, not just how many you have, etc.
I guess you could calculate specificity for all rules and then provide things like;
<element>
The text was updated successfully, but these errors were encountered:
Use specificity npm module
Sorry, something went wrong.
Example:
{ "metrics": { "specificityIdAvg": 0.05, "specificityIdTotal": 35, "specificityClassAvg": 1.25, "specificityClassTotal": 872, "specificityTagAvg": 0.78, "specificityTagTotal": 548 } }
analyze-css:specificity .search-result figure.image:hover > .price: 041 +0ms analyze-css:specificity #slideshow > form input[type="text"]: 112 +0ms
This is just awesome! Thanks! :D
macbre
Successfully merging a pull request may close this issue.
Would be cool addition to include CSS specificity into the metrics provided.
Specificity is great as it gives you information about what your rules are actually made up of, not just how many you have, etc.
I guess you could calculate specificity for all rules and then provide things like;
<element>
specificitiesThe text was updated successfully, but these errors were encountered: