Skip to content
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

Use "direct" as the message type when sending direct/private messages. #5725

Open
laurynmm opened this issue Apr 26, 2023 · 0 comments · May be fixed by #5728 or dashwave-test/zulip-mobile#12
Open

Use "direct" as the message type when sending direct/private messages. #5725

laurynmm opened this issue Apr 26, 2023 · 0 comments · May be fixed by #5728 or dashwave-test/zulip-mobile#12
Assignees

Comments

@laurynmm
Copy link

Zulip servers (at API feature level 174) support "direct" as the preferred message type for direct/private messages when sending messages and sending typing notifications; see zulip/zulip#25154.

For servers at this feature level, when sending direct messages (POST /messages), the mobile app should switch to using the new preferred "direct" value for direct messages.

For typing notifications, the default value was switched from "private" to "direct", so no changes need to be made by clients if the default is being used for direct/private message typing notifications.

See this #api design conversation for more context and discussion on the type parameter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment