Parsing error for template tags within classes on v11.11.0

[Techn1x]

I just bumped to eslint-plugin-ember 11.11.0 which consumes this PR #1920

However, now all of my GTS and GJS files seem to cause eslint parsing errors where they use the <template> tag within a class.

Within a class

Parsing error: Unexpected token. A constructor, method, accessor, or property was expected

Within a TOC

Parsing error: '>' expected

Here's an example component

and the error

eslint output

Relevant packages installed;
eslint 8.47
eslint-plugin-ember 11.11.0
ember-template-lint 5.11.2
ember-template-lint-plugin-prettier 5.0.0
prettier-plugin-ember-template-tag 1.0.2

[Techn1x]

A suggestion made here was to not specify a parser #1920 (comment)

Unfortunately, that does not seem to resolve the issue (I've commented out my typescript-eslint parser in my eslintrc.js file)

(note: I also tried plugin:@typescript-eslint/base instead of recommended for the plugin, no luck with that either)

[bmish]

As mentioned in #1920 (comment), if #1920 is a breaking change, we will need to revert it.

[Techn1x]

After some messing around, what does fix it, is if I place the ember config after the typescript-eslint config, as well as commenting out the parser. recommended or base doesn't seem to matter for the typescript-eslint config here.

The parsing errors I mentioned go away (I just get a whole bunch of different ones, but I don't think they're related)

[bmish]

We can't control what order people set their configs in or whether they use a parser globally. So it sounds like a breaking change.

@patricklx let's do a revert then. Is there another approach you'd like to try that isn't breaking? Or an acceptable breaking change that we should save for a major release?

[Techn1x]

Just FWIW: the @typescript-eslint/base config overrides the parser here

https://github.com/typescript-eslint/typescript-eslint/blob/5ee1dfe872f67cb504c89e95b1450a65802e11a8/packages/eslint-plugin/src/configs/base.ts#L9

[patricklx]

yes, that's what ember plugin also does in the recommended config. But eslint does not override the parser if its specified globally in the config :(