aspect-build / aspect-build/rules_lint
[FR]: Allow opt-in with tags in addition to existing 'nolint' opt-out
- Dominant language
- Starlark
- Stars
- 154
- Forks
- 125
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 20
Description
### What is the current behavior?
This feature does not exist today.
### Describe the feature
Currently, when we introduce a lint, there is now support to [opt-out with `no-lint`](github.com/aspect-build/rules_lint/blob/main/docs/linting.md#ignoring-targets).
When introducing linter(s) in a larger repository, it'd be easier if the opposite were possible, i.e. a `lint`-like opt-in tag where the linter runs ONLY on those targets.
Even nicer if possible to opt-in per linter. For eg., `lint-`
Contributor guide
Research direction
Start with docs/linting.md and its existing no-lint behavior. Trace how lint-related target tags are handled, then define the opt-in and per-linter tag behavior described in the issue. Done means linting runs only for opted-in targets, with per-linter opt-in supported if feasible, and the documentation reflects the behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100