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

Support using "direct" as the message "type" for private messages. #779

Open
laurynmm opened this issue Apr 24, 2023 · 0 comments
Open

Support using "direct" as the message "type" for private messages. #779

laurynmm opened this issue Apr 24, 2023 · 0 comments

Comments

@laurynmm
Copy link

laurynmm commented Apr 24, 2023

As follow-up to zulip/zulip#25154 (which fixed zulip/zulip#24960), we should:

  • Update sending messages (POST /messages) to support using "direct" as the message type for direct/private messages.
  • Auto-translate "direct" to "private" for servers that it knows via the the Client initialization check on the API feature level don't support it; "direct" was introduced at API feature level 174.

See #api design > message type parameter, #24960 for relevant context and discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant