mirror of
https://github.com/zulip/zulip.git
synced 2025-11-03 05:23:35 +00:00
api_docs: Update scheduled_message docs to specify empty string topic.
We missed to update this section of the docs while working on feature level 334.
This commit is contained in:
committed by
Tim Abbott
parent
5f709245c0
commit
d4ae480985
@@ -6353,6 +6353,16 @@ paths:
|
||||
Clients should use the `max_topic_length` returned by the
|
||||
[`POST /register`](/api/register-queue) endpoint to determine
|
||||
the maximum topic length.
|
||||
|
||||
Note: When the value of `realm_empty_topic_display_name` found in
|
||||
the [POST /register](/api/register-queue) response is used for this
|
||||
parameter, it is interpreted as an empty string.
|
||||
|
||||
When [topics are required](/help/require-topics), this parameter can't
|
||||
be `"(no topic)"`, an empty string, or `realm_empty_topic_display_name`.
|
||||
|
||||
**Changes**: Before Zulip 10.0 (feature level 334), empty string
|
||||
was not a valid topic name for channel messages.
|
||||
type: string
|
||||
example: Castle
|
||||
scheduled_delivery_timestamp:
|
||||
@@ -6517,6 +6527,16 @@ paths:
|
||||
Clients should use the `max_topic_length` returned by the
|
||||
[`POST /register`](/api/register-queue) endpoint to determine
|
||||
the maximum topic length.
|
||||
|
||||
Note: When the value of `realm_empty_topic_display_name` found in
|
||||
the [POST /register](/api/register-queue) response is used for this
|
||||
parameter, it is interpreted as an empty string.
|
||||
|
||||
When [topics are required](/help/require-topics), this parameter can't
|
||||
be `"(no topic)"`, an empty string, or `realm_empty_topic_display_name`.
|
||||
|
||||
**Changes**: Before Zulip 10.0 (feature level 334), empty string
|
||||
was not a valid topic name for channel messages.
|
||||
type: string
|
||||
example: Castle
|
||||
scheduled_delivery_timestamp:
|
||||
|
||||
Reference in New Issue
Block a user