-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add API support for using "direct" as the message "type" for private messages #24960
Comments
Hello @zulip/server-api members, this issue was labeled with the "area: api" label, so you may want to check it out! |
@timabbott - Yeah, assigning to me makes sense. I already noted this down as a follow-up in the work I'm doing on #24806. |
@laurynmm We noticed that you have not made any updates to this issue or linked PRs for 10 days. Please comment here if you are still actively working on it. Otherwise, we'd appreciate a quick If we don't hear back, you will be automatically unassigned in 4 days. Thanks! |
For endpoints with a `type` parameter to indicate whether the message is a stream or direct message, `POST /typing` and `POST /messages`, adds support for passing "direct" as a value for direct messages. Maintains support for "private" as a deprecated alias for direct messages. Fixes zulip#24960.
For endpoints with a `type` parameter to indicate whether the message is a stream or direct message, `POST /typing` and `POST /messages`, adds support for passing "direct" as a value for direct messages. Maintains support for "private" as a deprecated alias for direct messages. Fixes zulip#24960.
For endpoints with a `type` parameter to indicate whether the message is a stream or direct message, `POST /typing` and `POST /messages`, adds support for passing "direct" as a value for direct messages. Maintains support for "private" as a deprecated alias for direct messages. Fixes zulip#24960.
For endpoints with a `type` parameter to indicate whether the message is a stream or direct message, `POST /typing` and `POST /messages`, adds support for passing "direct" as the preferred value for direct messages, group and 1-on-1. Maintains support for "private" as a deprecated value to indicate direct messages. Fixes zulip#24960.
For endpoints with a `type` parameter to indicate whether the message is a stream or direct message, `POST /typing` and `POST /messages`, adds support for passing "direct" as the preferred value for direct messages, group and 1-on-1. Maintains support for "private" as a deprecated value to indicate direct messages. Fixes #24960.
For endpoints with a `type` parameter to indicate whether the message is a stream or direct message, `POST /typing` and `POST /messages`, adds support for passing "direct" as the preferred value for direct messages, group and 1-on-1. Maintains support for "private" as a deprecated value to indicate direct messages. Fixes zulip#24960.
Since we renamed "private messages" to "direct messages" in the UI, we should start thinking about API changes in line with this change. This issue is for the simplest one, which I think should be a Zulip 7.0 release goal: Allowing
send_message
(and similar things like typing notifications requests) to usedirect
rather thanprivate
for thetype
parameter.message_type_name: str = REQ("type")
@laurynmm can I assign this to you?
git grep private zerver/views/
suggests it may just be those two endpoints that need attention here.There's a significantly more difficult project of supporting a
direct
message type in events, which likely requires a client capability; the goal for this issue is just do the (mostly documentation, I think?) part of allowing things that send messages via the API to use the new name.The text was updated successfully, but these errors were encountered: