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
This came out of discussion around #7, but is a larger idea, hence new issue. The arguments we can pass via CLI are pretty long and generally not very clear. Instead, what if we had a config file (akin to webpack.config.js/eslintrc.js) to set up those rules? It could be a JS/JSON file that describes the desired report (format, audits, etc).
I'm thinking something like this for format, which kind of follows a babel-ish pattern for audits, where you can say the string name of the audit, or an array with the first item as the name, and second as arguments to the audit. This would also address the issue in #7 by allowing for repeating audits with different arguments.
- Adds the ability to store audit arguments in a configuration file named css-audit.config.js in the root of the project, fixes#8
- Supports multiple property-values audits from the config
Co-authored-by: Kelly Dwan <ryelle@users.noreply.github.com>
This came out of discussion around #7, but is a larger idea, hence new issue. The arguments we can pass via CLI are pretty long and generally not very clear. Instead, what if we had a config file (akin to
webpack.config.js
/eslintrc.js
) to set up those rules? It could be a JS/JSON file that describes the desired report (format, audits, etc).I'm thinking something like this for format, which kind of follows a babel-ish pattern for audits, where you can say the string name of the audit, or an array with the first item as the name, and second as arguments to the audit. This would also address the issue in #7 by allowing for repeating audits with different arguments.
Example:
We could also allow for a simple file like this— though maybe we should rename
all
&recommended
topreset:all
&preset:recommended
.The text was updated successfully, but these errors were encountered: