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

Recipient mix with username and firstname - Benutzername vs Vorname #854

Open
OneCreek opened this issue Aug 27, 2024 · 0 comments
Open

Comments

@OneCreek
Copy link

Describe the bug
Recipient is one user (M) having a public username (eg. Mpublic), the second recipient (K) doesn't have a public username.
See **Expected behavior": I expected to be able to mix username and firstname (when no username exists).

To Reproduce
'Store username not firstname' active.
Send message to "Mpublic; K"
But when "store username" is active, only Mpublic gets the message. When "store username" is deactivated, only K gets the message.

Expected behavior

"If the option is set and the user did not specify a public username in his telegram account, then the adapter will continue to use the firstname of the user."

„Benutzernamen statt Vornamen speichern“ in den Adaptereinstellungen aktiviert ist oder nicht.) Wenn die Option aktiviert ist und der Benutzer in seinem Telegram-Konto keinen öffentlichen Benutzernamen angegeben hat, verwendet der Adapter weiterhin den Vornamen des Benutzers."

So I expected to be able to mix username and firstname, since I use the username for M with Mpublic and K as firstname (no username existent). When "store username" is active, both Mpublic and K should get the message.

Versions:

  • Adapter version: v3.9.0
  • JS-Controller version: 6.0.9
  • Node version: v20.17.0
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