Bryan Mishkin

Currently, as the [rule doc](https://github.com/ember-template-lint/ember-template-lint/blob/master/docs/rule/no-whitespace-for-layout.md) says, this rule checks any text nodes for excess whitespace, including text inside or outside attributes. But I think it's a fair question to ask...

It may not be safe to fix this since they have different behavior? I'm not sure what the behavior should be. name | Example | Description -- | -- |...

What do you mean by this exactly?

Do you have a public example to link to? Is your plugin compiled to CJS? Or are you using flat config? (#376).

With ESM, you still have a build command and compiled CJS output, right? If this is the case, then the solution is normally to just ensure the build runs before...

@TheSonOfThomp I assume you mean a rule like [quotes](https://eslint.org/docs/latest/rules/quotes) that is configured with a string value instead of an object: `quotes: ["error", "double"]`. Yes, we haven't supported that type of...

An object API for rules is almost always a better choice as it allows you to add additional options later (much more future-proof). However, it would still be good for...

This is an interesting point. I hadn't considered that one might want to leave this option in place indefinitely. The original idea was that this option would only be used...

I'd be open to a new option (e.g. `--rule-list-align`) as a pass-thru to the markdown-table [align](https://github.com/wooorm/markdown-table#optionsalign) option we're using. While I generally prefer to have good default behavior and not...

I'm in favor of more automation for the release process, probably something like release-please in https://github.com/eslint/generator-eslint/pull/175. Contributions welcome if someone wants to improve it. For now, we have a command...