Skip to content
New issue

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

Support per-module checks #382

Open
RBusarow opened this issue Feb 18, 2022 · 1 comment
Open

Support per-module checks #382

RBusarow opened this issue Feb 18, 2022 · 1 comment
Labels
feature New feature or request

Comments

@RBusarow
Copy link
Member

In grotesquely large codebases with thousands of modules, the initial check can take enough time that it's no longer trivial to just execute against all modules. If a developer is modifying the dependencies in a single module -- probably somewhere in a middle layer of the dependency graph -- they should be able to execute against that single module.

@RBusarow RBusarow added the feature New feature or request label Feb 18, 2022
@tasomaniac
Copy link
Contributor

For some rules, just starting from that module works. But some others, it may be required to go up until the root and cover ancestors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants