The .herb/rules/*.mjs custom rule mechanism works well per-project, but we'd love two
things for using it across an organization with many repos:
- Shareable rules — loading custom rules from an npm package (or module path),
not just the local .herb/rules/ directory, so we can publish a rule set once and
reuse it everywhere (similar to ESLint plugins). Copying .mjs files into each repo
is hard to version and keep in sync.
- Testing — a documented/official way to unit-test a custom rule (something like
ESLint's RuleTester), or even just docs on the recommended pattern using the
existing API.
Are these on the radar, or is there already a recommended approach I've missed?
(Possibly related: #1756, where local custom rules hit a dependency-resolution issue.)
The
.herb/rules/*.mjscustom rule mechanism works well per-project, but we'd love twothings for using it across an organization with many repos:
not just the local
.herb/rules/directory, so we can publish a rule set once andreuse it everywhere (similar to ESLint plugins). Copying
.mjsfiles into each repois hard to version and keep in sync.
ESLint's RuleTester), or even just docs on the recommended pattern using the
existing API.
Are these on the radar, or is there already a recommended approach I've missed?
(Possibly related: #1756, where local custom rules hit a dependency-resolution issue.)