Select models and fields via settings #114
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Select models and fields via settings, allowing for more granular filtering of what is or isn't included in cleanup.
Note I didn't do anything different for
select_mode
given it got confusing fast, maybe it's easier to consider this as a layer on top of whatever app config has been selected, it's essentially select mode but more granular.Mostly I've based the setting syntax off of what
FIELDS
stores anyway, given it's quite similar to how other packages like cacheops are configured.Might be nice to
fnmatch
the model same as cacheops so you can do"core.*"
but I didn't bother at this point.This resolves #113.