-
-
Notifications
You must be signed in to change notification settings - Fork 483
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
Base manager can now be used for clean_duplicate_history #804
Conversation
Codecov Report
@@ Coverage Diff @@
## master #804 +/- ##
==========================================
+ Coverage 97.47% 97.88% +0.40%
==========================================
Files 18 18
Lines 992 992
Branches 151 151
==========================================
+ Hits 967 971 +4
+ Misses 12 9 -3
+ Partials 13 12 -1
Continue to review full report at Codecov.
|
Would you mind adding tests in |
Test added |
@nick-traeger This is looking like a nice contribution for folks who use custom managers to filter their models' queries. Would you go through the checklist (from your initial comment) and make sure you've completed the necessary items? Most are already complete or very minor updates. I checked off a couple for you that are clearly already done. Also, would you mind adding a short note about usage of the new option in the Utils docs page? |
@nick-traeger this needs to be rebased. |
1 similar comment
@nick-traeger this needs to be rebased. |
Description
clean_duplicate_history uses
objects
as manager. This has now been changed to_default_manager
and an option added to use_base_mananger
.Related Issue
none
Motivation and Context
We use a manager to filter records by default, however we want to remove all records from duplicates.
How Has This Been Tested?
The command was first run without parameters and then with the new
--base-manager
parameter.Screenshots (if appropriate):
none
Types of changes
Checklist:
make format
command to format my codeAUTHORS.rst
CHANGES.rst