Fix command matching to support both /command and command formats#15
Merged
Fix command matching to support both /command and command formats#15
Conversation
Commands in commands_config.json without a leading "/" now work correctly when users prefix them with "/". The fix normalizes command comparison by stripping leading "/" from both the user's input and config commands before matching, allowing flexible command usage regardless of how they're defined in the config.
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
2 participants
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.
Commands in commands_config.json without a leading "/" now work correctly when users prefix them with "/". The fix normalizes command comparison by stripping leading "/" from both the user's input and config commands before matching, allowing flexible command usage regardless of how they're defined in the config.