Fixed bug that prevented next_record and prev_record from using custo… #501
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.
…m manager names
Description
The manager name
history
had been hardcoded in the function calls forget_next_record
andget_prev_record
. This PR usesutils.get_history_manager_for_model
to allow these functions to be used with custom manager names.Related Issue
Fixes #500
Motivation and Context
Bug fix.
How Has This Been Tested?
Added tests for
next_record
andprev_record
on a model with custom manager nameScreenshots (if appropriate):
Types of changes
Checklist:
make format
command to format my codeAUTHORS.rst
CHANGES.rst