api docs: Update API docs and changelog for new setting.

The commit 2c1a87166c did not properly
document the new feature in the changelog; while I was at it, I wrote
more detail in the field's description.
This commit is contained in:
Tim Abbott 2021-11-23 14:05:31 -08:00
parent 5607712794
commit d860b8e568
2 changed files with 13 additions and 3 deletions

View File

@ -20,6 +20,11 @@ format used by the Zulip server that they are interacting with.
## Changes in Zulip 5.0 ## Changes in Zulip 5.0
**Feature level 110**
* [`POST /register`](/api/register-queue): Added
`server_web_public_streams_enabled` to the response.
**Feature level 109** **Feature level 109**
* [`POST /register`](/api/register-queue), [`GET * [`POST /register`](/api/register-queue), [`GET

View File

@ -11105,9 +11105,14 @@ paths:
description: | description: |
Present if `realm` is present in `fetch_event_types`. Present if `realm` is present in `fetch_event_types`.
Whether web public streams are enabled in the server. Similar topic_name The value of the `WEB_PUBLIC_STREAMS_ENABLED` Zulip server level
`realm_enable_spectator_access` but based on the `WEB_PUBLIC_STREAMS_ENABLED` setting. A server that has disabled this setting intends to not offer [web
Zulip server level setting. public streams](/help/web-public-streams) to realms it hosts. (Zulip Cloud
defaults to `True`; self-hosted servers default to `False`).
Clients should use this to determine whether to offer UI for the
realm-level setting for enabling we-public streams
(`realm_enable_spectator_access`).
**Changes**: New in Zulip 5.0 (feature level 110). **Changes**: New in Zulip 5.0 (feature level 110).
event_queue_longpoll_timeout_seconds: event_queue_longpoll_timeout_seconds: