Repository navigation
feat(telegram): add command aliases, the command menu and bot mentions - #60
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Last step of #56: commands barely worked on Telegram.
/日程@nbtca_botand@nbtca_botmentions were read as plain text, and there was no command menu.[Command]takes an optionalAlias:/schedule,/next,/mc,/events,/ticketsand/summary. Both the reflection path and the source generator pass it through./aliasand/alias@nbtca_botto the command and ignores commands addressed to other bots./日程works too.@nbtca_botbecomes an at, so AIChat can be mentioned on Telegram.setMyCommandswith the aliases and/help.帮助lists/alias <参数> — 描述. QQ gets the same reply as before; a new test pins its text.Closes #56