Port over gjs/gts relevant ember-template-lint

Author: NullVoxPopuli

README.md

@@ -0,0 +1,79 @@
+# ember/template-builtin-component-arguments
+
+💼 This rule is enabled in the following [configs](https://github.com/ember-cli/eslint-plugin-ember#-configurations): `strict-gjs`, `strict-gts`.
+
+<!-- end auto-generated rule header -->
+
+✅ The `extends: 'recommended'` property in a configuration file enables this rule.
+
+The builtin `Input` component has several arguments that match attributes
+of the lower-case `input` HTML element. These arguments should be set via e.g.
+`@type`, instead of `type`, but it is easy to forget and can cause subtle
+issues.
+
+This rule warns about `Input` component invocations that use the following attributes instead of arguments:
+
+- `checked`
+- `type`
+- `value`
+
+The builtin `Textarea` component has several arguments that match properties
+of the lower-case `textarea` HTML element. These arguments should be set via e.g.
+`@value`, instead of `value`, but it is easy to forget and can cause subtle
+issues.
+
+This rule warns about `Textarea` component invocations that use the following attributes instead of arguments:
+
+- `value`
+
+Please note that this rule currently only warns about these three attributes on
+the `Input`, and one property on the `Textarea` components, but might be extended in the future to also warn about
+other attributes or builtin components.
+
+## Examples
+
+This rule **forbids** the following:
+
+```hbs
+<Input type='text' size='10' />
+```
+
+```hbs
+<Input @type='checkbox' checked />
+```
+
+```hbs
+<Textarea value="Hello, Tom!" /></Textarea>
+```
+
+This rule **allows** the following:
+
+```hbs
+<input type='text' size='10' />
+```
+
+```hbs
+<Input @type='text' size='10' />
+```
+
+```hbs
+<Input @type='checkbox' @checked={{true}} />
+```
+
+```hbs
+<Textarea @value="Hello, Tom!" /></Textarea>
+```
+
+## Migration
+
+- Add the `@` character in front of the relevant attributes to convert them
+  into component argument
+
+## Related Rules
+
+- [template-no-unknown-arguments-for-builtin-components](template-no-unknown-arguments-for-builtin-components.md)
+
+## References
+
+- [`Input` component API documentation](https://api.emberjs.com/ember/release/classes/Ember.Templates.components/methods/Input?anchor=Input)
+- [`Textarea` component API documentation](https://api.emberjs.com/ember/release/classes/Ember.Templates.components/methods/Textarea?anchor=Textarea)

docs/rules/template-block-indentation.md

@@ -0,0 +1,38 @@
+# ember/template-inline-link-to
+
+💼 This rule is enabled in the following [configs](https://github.com/ember-cli/eslint-plugin-ember#-configurations): `strict-gjs`, `strict-gts`.
+
+🔧 This rule is automatically fixable by the [`--fix` CLI option](https://eslint.org/docs/latest/user-guide/command-line-interface#--fix).
+
+<!-- end auto-generated rule header -->
+
+Disallows the inline form of the `link-to` component and enforces the block form instead.
+
+Ember's `link-to` component has both an inline form and a block form. This rule forbids the inline form.
+
+## Examples
+
+This rule **forbids** the following (inline form):
+
+```hbs
+{{link-to 'Link text' 'routeName' prop1 prop2}}
+```
+
+This rule **allows** the following (block form):
+
+```hbs
+{{#link-to 'routeName' prop1 prop2}}Link text{{/link-to}}
+```
+
+## Rationale
+
+The block form is a little longer but has advantages over the inline form:
+
+- It maps closer to the use of HTML anchor tags which wrap their inner content.
+- It provides an obvious way for developers to put nested markup and components inside of their link.
+- The block form's argument order is more direct: "link to route". The inline form's argument order is somewhat ambiguous (link text then link target). This is opposite of the order in HTML (`href` then link text).
+
+## References
+
+- [Ember guides/routing](https://guides.emberjs.com/release/routing/linking-between-routes/#toc_the-linkto--component)
+- [Ember api/LinkTo component](https://api.emberjs.com/ember/release/classes/Ember.Templates.components/methods/LinkTo?anchor=LinkTo)

docs/rules/template-builtin-component-arguments.md

@@ -0,0 +1,49 @@
+# ember/template-modifier-name-case
+
+💼 This rule is enabled in the following [configs](https://github.com/ember-cli/eslint-plugin-ember#-configurations): `strict-gjs`, `strict-gts`.
+
+🔧 This rule is automatically fixable by the [`--fix` CLI option](https://eslint.org/docs/latest/user-guide/command-line-interface#--fix).
+
+<!-- end auto-generated rule header -->
+
+Requires dasherized names for modifiers.
+
+Modifiers should use dasherized names when being invoked, not camelCase. This is a stylistic rule that will prevent you from using camelCase modifiers, requiring you to use dasherized modifier names instead.
+
+## Examples
+
+This rule **forbids** the following:
+
+```hbs
+<div {{didInsert}}></div>
+```
+
+```hbs
+<div {{onFocus}}></div>
+```
+
+```hbs
+<div {{modifier 'didInsert'}}></div>
+```
+
+This rule **allows** the following:
+
+```hbs
+<div {{did-insert}}></div>
+```
+
+```hbs
+<div {{on-focus}}></div>
+```
+
+```hbs
+<div {{modifier 'did-insert'}}></div>
+```
+
+## See Also
+
+- [named-functions-in-promises](named-functions-in-promises.md)
+
+## References
+
+- [Template syntax guide - Modifiers](https://guides.emberjs.com/release/components/template-syntax/#toc_modifiers)

docs/rules/template-eol-last.md

@@ -1,5 +1,7 @@
 # ember/template-no-bare-yield
 
+💼 This rule is enabled in the following [configs](https://github.com/ember-cli/eslint-plugin-ember#-configurations): `strict-gjs`, `strict-gts`.
+
 <!-- end auto-generated rule header -->
 
 ✅ The `extends: 'plugin:ember/strict-gjs'` or `extends: 'plugin:ember/strict-gts'` property in a configuration file enables this rule.

docs/rules/template-inline-link-to.md

@@ -0,0 +1,75 @@
+# ember/template-no-curly-component-invocation
+
+💼 This rule is enabled in the following [configs](https://github.com/ember-cli/eslint-plugin-ember#-configurations): ✅ `recommended`, `strict-gjs`, `strict-gts`.
+
+<!-- end auto-generated rule header -->
+
+Disallows curly component invocation syntax. Use angle bracket syntax instead.
+
+There are two ways to invoke a component in a template: curly component syntax
+(`{{my-component}}`), and angle bracket syntax (`<MyComponent />`). The
+difference between them is syntactical. You should favour angle bracket syntax
+as it improves readability of templates, i.e. disambiguates components from
+helpers, and is also the future direction Ember is going with the Octane
+Edition.
+
+This rule checks all the curly braces in your app and warns about those that
+look like they could be component invocations.
+
+## Examples
+
+This rule **forbids** the following:
+
+```hbs
+{{foo-bar}}
+```
+
+```hbs
+{{nested/component}}
+```
+
+```hbs
+{{#foo-bar}}content{{/foo-bar}}
+```
+
+This rule **allows** the following:
+
+```hbs
+{{foo bar}}
+```
+
+```hbs
+<FooBar />
+```
+
+```hbs
+<Nested::Component />
+```
+
+## Configuration
+
+This rule accepts an options object with the following properties:
+
+- `allow` (default: `[]`) - Array of component names to allow in curly syntax
+- `disallow` (default: `[]`) - Array of component names to disallow in curly syntax
+- `requireDash` (default: `false`) - Require dashes in component names
+- `noImplicitThis` (default: `true`) - Don't allow implicit `this` references
+
+```js
+// .eslintrc.js
+module.exports = {
+  rules: {
+    'ember/template-no-curly-component-invocation': [
+      'error',
+      {
+        allow: ['some-helper'],
+        disallow: [],
+      },
+    ],
+  },
+};
+```
+
+## References
+
+- [Ember Guides - Angle Bracket Syntax](https://guides.emberjs.com/release/components/template-syntax/#toc_angle-bracket-syntax)