fix: support usage of . in keyboard user-events#40
Merged
Conversation
crutchcorn
approved these changes
May 31, 2025
commit: |
Contributor
Author
|
Hey @crutchcorn, can this be merged or did you need something more before merging? |
Owner
|
Whoops. Sorry, this LGTM. Let me run CI/CD real fast |
crutchcorn
approved these changes
Sep 18, 2025
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.
What:
Adds a period (".") into the current user-event keyboard map.
Why:
Currently, the following code produces unexpected results:
outputs the following into the console:
How:
Updated the
defaultKeyMapto contain a value for.(\x2ehex code)Checklist:
(I believe it's unnecessary to update tests for this as I didn't see existing specs that covered this keyMap, but correct me if I'm wrong)