docs: Add community_topic_editing_limit_seconds value to docs.

This was added to the response in e242ddc. Specifying the value
makes sure that the user does not have to dig in the commit history.
This commit is contained in:
Kaustubh Nair 2020-09-08 19:36:25 +05:30 committed by Tim Abbott
parent 57ad171112
commit acf31f8934
1 changed files with 2 additions and 1 deletions

View File

@ -157,7 +157,8 @@ No changes; feature level used for Zulip 3.0 release.
* [`POST /register`](/api/register-queue): Added * [`POST /register`](/api/register-queue): Added
`realm_community_topic_editing_limit_seconds` to the response, the `realm_community_topic_editing_limit_seconds` to the response, the
time limit before community topic editing is forbidden. A `null` time limit before community topic editing is forbidden. A `null`
value means no limit. value means no limit. This was previously hard-coded in the server
as 86400 seconds (1 day).
* [`POST /register`](/api/register-queue): The response now contains a * [`POST /register`](/api/register-queue): The response now contains a
`is_owner`, similar to the existing `is_admin` and `is_guest` fields. `is_owner`, similar to the existing `is_admin` and `is_guest` fields.
* [`POST /set-typing-status`](/api/set-typing-status): Removed legacy support for sending email * [`POST /set-typing-status`](/api/set-typing-status): Removed legacy support for sending email