mirror of https://github.com/zulip/zulip.git
f6e0171d02
It happens that whether you add a reaction or remove a reaction, we send the exact same fields, just using a different op code. This sort of symmetry is actually kind of rare, as usually "add" events have more fields, and "remove" events might just send an id of something to remove. Our openapi schema treats these as two seperate events, so we are more consistent with it, and it helps our schema-checking tooling for node fixtures, too. Note that we now have to exempt the two events from our openapi checks, due to the is_mirror_dummy field in the deprecated user block. We can decide how to handle this later--one possibility is to just add it as an optional field on the event_schema side. |
||
|---|---|---|
| .. | ||
| data_import | ||
| lib | ||
| management | ||
| migrations | ||
| openapi | ||
| templatetags | ||
| tests | ||
| tornado | ||
| views | ||
| webhooks | ||
| worker | ||
| __init__.py | ||
| apps.py | ||
| context_processors.py | ||
| decorator.py | ||
| filters.py | ||
| forms.py | ||
| logging_handlers.py | ||
| middleware.py | ||
| models.py | ||
| signals.py | ||