fix(developer): do not treat backslash as a string escape in syntax highlighting 🍒 🏠#15005
Merged
mcdurdin merged 1 commit intostable-18.0from Oct 27, 2025
Conversation
github-actions
bot
added
developer/
developer/ide/
cherry-pick
User Test ResultsTest specification and instructions User tests are not required |
keymanapp-test-bot
bot
changed the title
mcdurdin
deleted the
fix/developer/cherry-pick/14988-string-escape-syntax-highlight
branch
8 tasks
Collaborator
|
Changes in this pull request will be available for download in Keyman version 18.0.244 |
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
3 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.
Adjust two incorrect rules that caused backslash to be treated as an escape in strings in syntax highlighting in .kmn language.
Fixes: #14988
Test-bot: skip
Build-bot: skip
Cherry-pick-of: #15001