incorrect append double slash text while onEnter called

[mortalYoung]

Does this issue occur when all extensions are disabled?: Yes/No

• VS Code Version: 1.99.3
• OS Version: MacOS
• Language: TypeScript

Steps to Reproduce:

1. type text in editor [/</g, />/g]
2. do enter after ,

Expect

the editor value be:

[/</g, 
/>/g]

Actual

[/</g, 
// />/g]

Maybe

It matches this rule.

vscode/extensions/typescript-basics/language-configuration.json

Lines 250 to 261 in 2b7f830

	{
	"beforeText": {
	"pattern": "(?<!\\\\)(?<!\\w:)\/\/.*"
	},
	"afterText": {
	"pattern": "^(?!\\s*$).+"
	},
	"action": {
	"indent": "none",
	"appendText": "// "
	}
	},

Normally, the beforeText which is [/</g not matches the pattern.

But at some situation i don't know, the beforeText be transformed to [//g which lost the character < and make it matched.

[RedCMD]

caused by:

• Explore removing brackets of language configuration file from the string/regex before evaluating indentation #209862

cc @aiday-mar
#236296 would fix all the issues
being able to correctly remove custom characters from any single tokentype (string, comment, regex, other)

related:

• Continue comment when enter is pressed #26694
• Incorrect indentation inside of comments #208232
• [Bug]: Incorrect indentation when object contains string keys #209517
• Expand usage of standard token type inside of the auto indentation to ignore comments and strings for indentation #209519
• Auto indent on paste is incorrect in strings #209418
• Skip lines that are strictly inside of a multi-line string for indentation evaluation #209859
• Skip comments entirely when evaluating indentation #209861
• Explore removing brackets of language configuration file from the string/regex before evaluating indentation #209862
• Test correct indentation when strings, comments, regex tokens contain brackets of language configuration #213561
• Auto indent issue: Lua multiline quotes [[...]] conflict with #210641 which removes brackets before passing text to indent rules #223606
• Enter inserts // #233675
• onEnter Indentation Rules: Ignoring double slashes inside of strings #235712
• Strip characters from "onEnterRules" string #236296
• 🚨 Stop adding comment when enter is pressed #236828
• "Continue comment on enter" unexpectedly inserts comment when it should not #238791
• Comment is getting added randomly when pressing enter on a line where a URI is defined #239481
• Ignoring URLs when adding line comment onEnter  #239576
• Extraneous comment added upon "Select all occurrences" + Enter #241108
• JavaScript comment continuation on enter false positive with "//" in string literals #241125
• Bug: Enter Press After ‘//’ Breaks Line and Converts Code to Comment in JavaScript #241802
• When typing enter after a double slash, the line-breaking javascript code is automatically commented out by mistake #242658

[aiday-mar]

I wonder if instead we should directly remove the regex rule all together just as we remove the brackets before evaluating the onEnter rules. Perhaps we could even entirely remove comments when evaluating indentation. But this could lead to unexpected consequences depending on how extension authors have defined their onEnter rules. I am hoping that when we implement tree sitter based indentation, this will no longer be an issue because we will evaluate the rules based on semantics and not regex rules.