mirror of https://github.com/zulip/zulip.git
53da9ef072
The change in behavior suggesting the need for this clarification is summarized below, as discussed in the following topic: https://chat.zulip.org/#narrow/stream/378-api-design/topic/update_message.20default.20notifications The new text is as suggested by Greg Price. The change at feature level 152 made the moving of topics within and between streams more consistent, by applying the optional parameters introduced for the latter to both cases (`send_notification_to_[new|old]_thread`). The default for the `old` notification value was changed to `false` at this point, but the equivalent `new` value was not. This introduced a change in behavior for existing clients of the API when moving topics within streams, which now always produce a notification message by default. The improved consistency and default behavior for new API clients were considered primary factors at the time of this change, overriding concerns over backwards compatbility. |
||
---|---|---|
.. | ||
include | ||
api-doc-template.md | ||
api-keys.md | ||
changelog.md | ||
client-libraries.md | ||
configuring-python-bindings.md | ||
construct-narrow.md | ||
create-scheduled-message.md | ||
create-stream.md | ||
deploying-bots.md | ||
http-headers.md | ||
incoming-webhooks-overview.md | ||
incoming-webhooks-walkthrough.md | ||
index.md | ||
installation-instructions.md | ||
integrations-overview.md | ||
missing.md | ||
non-webhook-integrations.md | ||
outgoing-webhooks.md | ||
real-time-events.md | ||
rest-error-handling.md | ||
rest.md | ||
roles-and-permissions.md | ||
running-bots.md | ||
send-message.md | ||
sidebar_index.md | ||
writing-bots.md |