Repository navigation
Correct how command names derive from class names - #1507
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
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.
CLAUDE.md said a class
FooBarCommandis reached as/foobar. A command file in a commands path is registered as/foo_bar(classNameToCommandName()inserts an underscore before each inner capital)./foobarresolves only through the fallback lookup, which builds a class name in a defaultLongman\TelegramBot\Commands\*Commandsnamespace and relies on PHP class names being case-insensitive, so it fails for a class in a custom namespace. The$nameproperty sets the command name only for classes added throughaddCommandClass().Checked at runtime: in a default namespace both
foo_barandfoobarresolve toFooBarCommand; in a custom namespacebaz_quxresolves toBazQuxCommandandbazquxresolves to nothing.