-
-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
Allow sending messages given a user's full_name
using the API
#32419
Comments
can i contribute in this issues |
Hello @sa-fw-an! Thanks for your interest in Zulip! You have attempted to claim an issue without the label "help wanted". You can only claim and submit pull requests for issues with the help wanted label. If this is your first time here, we recommend reading our guide for new contributors before getting started. |
yes, of course!) If you need my approval ))) |
Hello @zulip/server-api members, this issue was labeled with the "area: api" label, so you may want to check it out! |
full_name
using the API
I fixed the title to be less confusing to folks who work on the project. Nobody should work on implementing this, in that we haven't decided this is a feature we want in Zulip. @Welets can you talk about how you're hoping to use this feature with some detail on what you're trying to do, to help us discuss whether we want it? |
@timabbott Thanks for the clarification. I do have a solution for this feature that could be implemented or considered for future development. I’m also ready to work on it if the feature is needed. |
Can I contribute to this issue? |
@timabbott Of course! We have several systems that we want to connect with zulip, but not all of them require the presence of Email. Or there are people who prefer to have several Emails for different services. Which will not give the proper level of automation, because you will constantly have to build a "matching" base where pairs of "values" are, for example, gmail: zulipEmail, or username: zulipId. However, if you have user_name, there will be no such problems. Which will make the integration simple and enjoyable |
@timabbott good day. I am written requested by the status "feedback wanted" feedback. if you have seen. I apologize for persistence. And if suddenly not, then it is above suitable for review. |
Problem Statement:
unable to send message to user via @user_name request
Unable to use anything other than Email and user_id:
currently curl and other requests to send to user's private messages use the format
--data-urlencode 'to=user_id'
or--data-urlencode 'to=Email'
Proposed Feature Enhancements:
Ability to use username as
--data-urlencode 'to=username'
to use this marker correctly, make sure that the "use same names" function is disabledThe text was updated successfully, but these errors were encountered: