Ambiguity between MatchTypeCommand and MatchTypeContains

[ruizlenato]

I think it's very confusing that MatchTypeCommand does the same thing as MatchTypeContains, except that it considers a / before.
MatchTypeCommand should be MatchTypeCommandStartOnly.

And it should consider the bot's username.
For example, I have a bot with the username @Mytestbot.

And I have a command /start. If I use /start@mytestbot, the bot ignores it.

[parmetra]

Hello! You can check out the options for handling commands like /start@mytestbot here - #174

[ruizlenato]

Hello! You can check out the options for handling commands like /start@mytestbot here - #174
I saw that, but my question remains. Especially the first part.

Second, the linked issue does not resolve my question because it addresses a mitigation for something bad in the library.

[ruizlenato]

ruizlenato@5a5d0a2

I recently made a fork and changed the way I register handlers.
Instead of having multiple MatchType, I removed them in favor of regex. IMO, it's unnecessary code because the regex function can do everything that the removed MatchType did and much more.

If any maintainers find this interesting and want to bring it upstream, I can open a PR.