[BUG]: Interference with VSCode built-in formatting

[MiracleBlue]

Describe the bug
Hi there,

This extension seems to be interfering with some of VSCodes format-on-type features, such as brace expansion on enter.

So for example, when typing the following in a typescript file:

const thing = {<my cursor here>

Assuming your cursor is at the end of that line, hitting enter, I expect VSCode to automatically expand that to:

const thing = {
  <my cursor here>
}

However that was not happening, instead I was getting this:

const thing = {
<my cursor here>}

I kept messing with my auto formatting settings trying to figure out what was wrong, in the end when I ran bisect, it was only this extension which seemed to prevent that behaviour somehow.

To Reproduce
Steps to reproduce the behavior:

1. Open a typescript file (.ts)
2. Write the following text: const thing = {
3. Press the enter key
4. Result is not formatted properly by VSCode, ending up with:

const thing = {
}

Expected behavior
Result should end up being formatted correctly by VSCode built-in behaviour into this:

const thing = {
  <cursor here>
}

Screenshots
N/A

Additional context
Add any other context about the problem here.

Here's the output contents: https://gist.github.com/MiracleBlue/3966aa775e70cf0b69ed2700c159fbf3

[yCodeTech]

The problem is because VScode has inconsistencies in the property naming between the language config JSON file and the VScode API. An onEnter rule property in JSON is indent but in the API it's indentAction. And because this extension merges the internal auto-found language config JSON files with the extension's comment rules, VScode does not know how to handle the mixed formats, so it got confused when processing the onEnter rules.

I've normalized the properties so this is now fixed in the latest release v1.1.11.