zulip/zerver/openapi
Sahil Batra bb15b2d708 users: Send "update" events when deactivating or reactivating users.
We now send "realm_user/update" (and "realm_bot/update" for bots)
events with "is_active" field when deactivating and reactivating
users, including bots.

We would want to use "remove" event for a user losing access
to another user for #10970, so it is better to use "update"
event for deactivation as we only update "is_active" field
in the user objects and the clients still have the data for
deactivated users.

Previously, we used to send "add" event for reactivation along
with complete user objects, but clients should have the data
for deactivated users as well, so an "update" event is enough
like we do when deactivating users.
2023-11-02 08:31:12 -07:00
..
__init__.py
curl_param_value_generators.py codespell: Fix typos caught by codespell. 2023-10-09 11:55:15 -07:00
javascript_examples.js
javascript_examples.py
markdown_extension.py mypy: Enable new error explicit-override. 2023-10-12 12:28:41 -07:00
openapi.py api-docs: Check for deprecated at top level of endpoint docs. 2023-10-25 12:21:53 -07:00
python_examples.py typing_indicator: Add a 'stream_id' parameter to 'POST /typing'. 2023-10-12 09:53:09 -07:00
test_curl_examples.py ruff: Fix PERF401 Use a list comprehension to create a transformed list. 2023-08-07 17:23:55 -07:00
testing.yaml
zulip.yaml users: Send "update" events when deactivating or reactivating users. 2023-11-02 08:31:12 -07:00