fix(composer): support Chinese slash command trigger - #614
Open
Usernames686 wants to merge 1 commit into
Open
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.
Problem
When using a Chinese IME, the key that normally produces
/produces、, so users must switch input methods before opening slash commands.Fixes #597.
Fix
Treat
、as an input-level alias for/when triggering slash commands. The alias is normalized to the existing internal/trigger, and command selection still creates the canonical slash-command reference.The normalization is limited to slash-command triggering and token replacement. It does not replace normal Chinese punctuation in message content.
Tests
/still triggers slash commands、triggers the same slash command flow、remains unchanged/