Bert De Block

It seems this was done in https://github.com/ember-cli/ember-cli/pull/6552, so I guess we can close this?

Since this issue is quite old and the linting setup nowadays is pretty different, can we close this?

It's intended that we don't lint the invocation side: https://github.com/ember-template-lint/ember-template-lint/pull/2080#pullrequestreview-742090620

I think an option sounds good!

I could be mistaken / misunderstanding, but ESLint also errors when no files are found matching the provided pattern. That's why both ESLint and ember-template-lint support the `--no-error-on-unmatched-pattern` flag I...

There's also the [no-classic-components](https://github.com/ember-cli/eslint-plugin-ember/blob/master/docs/rules/no-classic-components.md) rule to enforce migrating to Glimmer components. No use of classic components will also mean no use of `@tagName` and `@classNames`, unless they are custom arguments...

Glimmer components don't have support for `tagName` and `classNames` as they don't have a wrapping element like classic components do. Everything DOM related needs to be defined inside the component...

FYI, https://github.com/ember-template-lint/ember-template-lint/issues/1870 seems like a similar issue.

Would `tabindex="-1"` work as well or is `tabindex="-1"` vs no `tabindex` attribute at all still a different thing?

AFAICT, the fix seems okay. You can't pass in attributes using the curly notation, so the first example only contains actual arguments. `data-test-foo` and `class` are valid argument names when...