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

Caching for baseline linting #443

Closed
akaihola opened this issue Jan 3, 2023 · 1 comment
Closed

Caching for baseline linting #443

akaihola opened this issue Jan 3, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@akaihola
Copy link
Owner

akaihola commented Jan 3, 2023

Is your feature request related to a problem? Please describe.
Linting became slower in #393 due to running each linter twice.

Describe the solution you'd like
In local development, the developer often re-runs Darker multiple times for the same branch, having effectively the same rev1 revision each time. The linting output is identical every time since baseline linting is done in a fresh clone of the repository at rev1. Linting output could be cached so the time spent on running linters could drop to half in the extreme case.

Describe alternatives you've considered
We could decide to not cache, and accept the slowdown.

@akaihola
Copy link
Owner Author

Moved to akaihola/graylint#27.

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

No branches or pull requests

1 participant