Get default user for bulk ops from middleware #677
Merged
+184
−4
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.
Description
Bulk utility operations such as
bulk_create_with_history
andbulk_update_with_history
were recently added to the library. Both functions allow you to specify a default user, or to specify the user on the object instances themselves using_history_user
. However, there's no easy way to get the current user in the same way that we get it for normal historical model creation. This PR updates those bulk create operations such that the user is the same user that would be applied if they were not bulk operations (unless you specifyTypes of changes
Checklist:
make format
command to format my codeAUTHORS.rst
CHANGES.rst