f8836547f1
|
||
|---|---|---|
| .. | ||
| 001-deprecations.js | ||
| 002-comment-id.js | ||
| 005-template-compile.js | ||
| 010-package-json.js | ||
| 020-theme-structure.js | ||
| 030-assets.js | ||
| 040-ghost-head-foot.js | ||
| 050-koenig-css-classes.js | ||
| 060-js-api-usage.js | ||
| 070-theme-translations.js | ||
| 080-helper-usage.js | ||
| 090-template-syntax.js | ||
| 100-custom-template-settings-usage.js | ||
| 110-page-builder-usage.js | ||
| 120-no-unknown-globals.js | ||
| README.md | ||
README.md
The gscan rule categories are coming from the need to make the failed checks more readable for the end user. They enable logical grouping and sensible order.
TODO
In the gscan performance project (cycle 3, 2021), we had to integrate one AST rule and we did so under the category 090-template-syntax. It's not correct, the category 090 should be deleted. The reason is that we don't want one category that contains all AST checks.
Instead we should make sure that AST rules can be run in any existing category like 020-theme-structure. There is no appetite to make this change right now, it could be done in the future if we want to spend time on it.