Closed
Bug 1204132
Opened 9 years ago
Closed 8 years ago
Remove _signal argument to various methods
Categories
(Marketplace Graveyard :: Code Quality, enhancement, P5)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mat, Unassigned)
Details
(Whiteboard: [ktlo][possible_future_need])
Some methods in zamboni (particularly ModelBase.update()) have a special _signal argument that can be set to prevent this method from firing signals like post_save. It makes code more complicated and harder to follow. We should not prevent signals from being sent, we should write the signal handlers correctly to avoid issues. One particular use-case we should look at is _signal=False passed in post_save handlers that do a .save() or .update() themselves. Maybe some of those handlers should be trigged on pre_save instead and just set the properties they want on the instance without triggering a .save()/.update(), letting the regular .save() call that is going to happen afterwards deal with saving the changes.
Updated•9 years ago
|
Priority: -- → P3
Whiteboard: [ktlo]
Updated•8 years ago
|
Severity: normal → enhancement
Priority: P3 → P5
Updated•8 years ago
|
Whiteboard: [ktlo] → [ktlo][possible_future_need]
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•