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

Allow sending messages given a user's full_name using the API #32419

Open
Welets opened this issue Nov 21, 2024 · 9 comments
Open

Allow sending messages given a user's full_name using the API #32419

Welets opened this issue Nov 21, 2024 · 9 comments

Comments

@Welets
Copy link

Welets commented Nov 21, 2024

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 disabled

@Adityakk9031
Copy link

Adityakk9031 commented Nov 21, 2024

can i contribute in this issues

@zulipbot
Copy link
Member

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.

@Welets
Copy link
Author

Welets commented Nov 22, 2024

can i contribute in this issues

yes, of course!) If you need my approval )))

@zulipbot
Copy link
Member

Hello @zulip/server-api members, this issue was labeled with the "area: api" label, so you may want to check it out!

@timabbott timabbott changed the title using the username as an argument to determine the recipient of the message Allow sending messages given a user's full_name using the API Nov 22, 2024
@timabbott
Copy link
Member

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?

@sa-fw-an
Copy link

@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.

@AnuragVerma06
Copy link

Can I contribute to this issue?

@Welets
Copy link
Author

Welets commented Nov 25, 2024

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 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

@Welets
Copy link
Author

Welets commented Dec 2, 2024

@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.

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

No branches or pull requests

6 participants