You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I expect is that I should be able to re-run lintmigrations with different options and get the latest result based on the current set of options. django-migration-linter should either not cache anything that is based on the current options or it should bust the cache whenever the options changed.
This is particularly problematic because caching is always enabled by default when you don't pass in --cache-path or --no-cache. It leads to extremely confusing behavior that the options from previous runs affects the result of current run.
The text was updated successfully, but these errors were encountered:
Suppose that I have an app with one erroneous file:
I can disable that warning with
--exclude-migration-test
:This is working well when passing
--no-cache
.However, when caching is enabled:
When I re-run the command again with
--exclude-migration-test
, the result seems to have become fixated to the previous option due to the cache:Same issue with
--warnings-as-errors
as well.What I expect is that I should be able to re-run
lintmigrations
with different options and get the latest result based on the current set of options. django-migration-linter should either not cache anything that is based on the current options or it should bust the cache whenever the options changed.This is particularly problematic because caching is always enabled by default when you don't pass in
--cache-path
or--no-cache
. It leads to extremely confusing behavior that the options from previous runs affects the result of current run.The text was updated successfully, but these errors were encountered: