mirror of https://github.com/zulip/zulip.git
1c5007461a
Currently we send a notification to the topic if it has been resolved or unresolved even if there is an immediate event of resolving and then unresolving or vice-versa. This adds a setting of RESOLVE_TOPIC_UNDO_GRACE_PERIOD_SECONDS under which if a topic has been unresolved after being resolved immediately and the last message was the notification of resolving, then delete the last message and don't send a new notification and vice-versa. We use the new message.type field to precisely identify relevant messages. Fixes #19181. Co-authored-by: Mateusz Mandera <mateusz.mandera@zulip.com> |
||
|---|---|---|
| .. | ||
| actions | ||
| data_import | ||
| integration_fixtures/nagios | ||
| lib | ||
| management | ||
| migrations | ||
| models | ||
| openapi | ||
| tests | ||
| tornado | ||
| transaction_tests | ||
| views | ||
| webhooks | ||
| worker | ||
| __init__.py | ||
| apps.py | ||
| context_processors.py | ||
| decorator.py | ||
| filters.py | ||
| forms.py | ||
| logging_handlers.py | ||
| middleware.py | ||
| signals.py | ||