-
Notifications
You must be signed in to change notification settings - Fork 132
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
Refactor submission deletion queryset #1808
Conversation
Should we add a test that it is now called? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. As @moshthepitt has mentioned, we could just add a test to check the post_save signal is called. May be use mocking?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
325d3bd
ee3516e
to
325d3bd
Compare
This is because .update() doesn't emit a post_save signal and doesn't call .save() on the Instance model Signed-off-by: Kipchirchir Sigei <[email protected]>
Signed-off-by: Kipchirchir Sigei <[email protected]>
…tion Signed-off-by: Kipchirchir Sigei <[email protected]>
325d3bd
to
9682942
Compare
Changes / Features implemented
.update()
since it doesn't call the Instance model's.save()
method.update()
method doesn't sendpost_save
signal required by google exports or any other micro serviceSteps taken to verify this change does what is intended
Side effects of implementing this change
Closes #