Port over ember-template-lint rule for gjs/gts

Revert .github changes

Remove attribute indentation rule. We have prettier for formatting concerns

Port over gjs/gts relevant ember-template-lint

cleanup

Add documentation and test files for removed ember rules

feat(rules): add template-require-valid-form-groups and template-template-length rules

- Introduced `template-require-valid-form-groups` rule to enforce proper grouping of form controls using `<fieldset>`/`<legend>` or WAI-ARIA roles.
- Added `template-template-length` rule to enforce size constraints on templates, allowing configuration for minimum and maximum line lengths.
- Updated documentation for existing rules to include configuration details.
- Added tests for both new rules to ensure correct functionality and error reporting.

Cleanup

Fix

fix

Update documentation links from ember-template-lint to eslint-plugin-ember

- Changed references in various rule documentation files to point to the new eslint-plugin-ember URLs instead of ember-template-lint.
- Updated tests to reflect the change in rule naming conventions.

Add scope checking to template-no-arguments-for-html-elements

Fix

oof

Cleanup

Enhance linting rules: refine messages and add checks for `this.attrs`, `this.this`, and yield scenarios

Refactor rule and tests for template-no-attrs-in-components: specify `this.attrs` usage and update examples

lint:fix

Fix AI garbage

ope

ope

In progress copying more tests over

Refactor lint rules and update test cases for improved clarity and functionality

Fixes

Docs updates

Fix

Author: Copilot

.gitignore

@@ -14,3 +14,4 @@ npm-debug.log
 
 # eslint-remote-tester
 eslint-remote-tester-results
+package-lock.json

CHANGELOG.md

@@ -139,6 +139,6 @@ arr.uniq();
 
 ## Related Rules
 
-- [no-array-prototype-extensions](https://github.com/ember-template-lint/ember-template-lint/blob/master/docs/rule/no-array-prototype-extensions.md) from ember-template-lint
+- [template-no-array-prototype-extensions](https://github.com/ember-cli/eslint-plugin-ember/blob/master/docs/rules/template-no-array-prototype-extensions.md) from eslint-plugin-ember
 - [no-function-prototype-extensions](no-function-prototype-extensions.md)
 - [no-string-prototype-extensions](no-string-prototype-extensions.md)

README.md

@@ -45,14 +45,14 @@ import didUpdate from '@ember/render-modifiers/modifiers/did-update';
 import willDestroy from '@ember/render-modifiers/modifiers/will-destroy';
 ```
 
-For more examples, see [the docs on ember-template-lint](https://github.com/ember-template-lint/ember-template-lint/blob/master/docs/rule/no-at-ember-render-modifiers.md).
+For more examples, see [the docs on eslint-plugin-ember](https://github.com/ember-cli/eslint-plugin-ember/blob/master/docs/rules/template-no-at-ember-render-modifiers.md).
 
 ## References
 
 - [Editions](https://emberjs.com/editions/)
 - [Octane Upgrade Guide](https://guides.emberjs.com/release/upgrading/current-edition/)
 - [Component Documentation](https://guides.emberjs.com/release/components/)
 - [Avoiding Lifecycle in Component](https://nullvoxpopuli.com/avoiding-lifecycle)
-- [The `ember-template-lint` version of this rule](https://github.com/ember-template-lint/ember-template-lint/blob/master/docs/rule/no-at-ember-render-modifiers.md)
+- [The `eslint-plugin-ember` version of this rule](https://github.com/ember-cli/eslint-plugin-ember/blob/master/docs/rules/template-no-at-ember-render-modifiers.md)
 - [`ember-modifier`](https://github.com/ember-modifier/ember-modifier)
 - [`@ember/render-modifiers`](https://github.com/emberjs/ember-render-modifiers) (deprecated)

docs/rules/no-array-prototype-extensions.md

@@ -109,7 +109,7 @@ export default helper(substring);
 
 ## Related Rules
 
-- ember-template-lint has a [no-triple-curlies](https://github.com/ember-template-lint/ember-template-lint/blob/master/docs/rule/no-triple-curlies.md) rule for the template equivalent of this rule.
+- eslint-plugin-ember has a [template-no-triple-curlies](https://github.com/ember-cli/eslint-plugin-ember/blob/master/docs/rules/template-no-triple-curlies.md) rule for the template equivalent of this rule.
 
 ## References
 

docs/rules/no-at-ember-render-modifiers.md

@@ -60,4 +60,4 @@ Accepts an array of the objects with the following options:
 ## Related Rules
 
 - The [no-restricted-imports](https://eslint.org/docs/rules/no-restricted-imports) or [import/no-restricted-paths](https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-restricted-paths.md) rules are the JavaScript import statement equivalent of this rule.
-- ember-template-lint has a [no-restricted-invocations](https://github.com/ember-template-lint/ember-template-lint/blob/master/docs/rule/no-restricted-invocations.md) rule for disallowing component usages.
+- eslint-plugin-ember has a [template-no-restricted-invocations](https://github.com/ember-cli/eslint-plugin-ember/blob/master/docs/rules/template-no-restricted-invocations.md) rule for disallowing component usages.

docs/rules/no-html-safe.md

@@ -6,60 +6,67 @@ Enforces a consistent ordering of attributes in template elements. This helps im
 
 ## Rule Details
 
-This rule enforces a consistent order for attributes on template elements. By default, it follows this order:
-
-1. `class`
-2. `id`
-3. `role`
-4. `aria-*` attributes
-5. `data-test-*` attributes
-6. `type`
-7. `name`
-8. `value`
-9. `placeholder`
-10. `disabled`
+This rule enforces a consistent order for attributes on template elements. By default, attributes are ordered by type group:
+
+1. **Arguments** — `@argName` (Glimmer component arguments)
+2. **Attributes** — standard HTML attributes like `class`, `id`, `role`
+3. **Modifiers** — `{{on "click" ...}}`, `{{did-insert ...}}`, etc.
+
+Within each group, attributes are sorted alphabetically by default.
+
+Additional groups (`splattributes` and `comments`) can be added to the ordering if needed.
+
+Hash pairs in curly invocations (mustache/block statements) are also alphabetized when `alphabetize` is enabled.
 
 ## Examples
 
 Examples of **incorrect** code for this rule:
 
 ```gjs
 <template>
-  <div id="main" class="container"></div>
+  <MyComponent class="btn" @onClick={{this.go}} @label="hi" />
 </template>
 ```
 
+In this example, `class` (an attribute) appears before `@onClick` and `@label` (arguments). Arguments should come first.
+
 ```gjs
 <template>
-  <button aria-label="Submit" role="button">Send</button>
+  <MyComponent @label="hi" @action={{this.go}} />
 </template>
 ```
 
+Here, `@label` and `@action` are out of alphabetical order within the arguments group.
+
 Examples of **correct** code for this rule:
 
 ```gjs
 <template>
-  <div class="container" id="main"></div>
+  <MyComponent @action={{this.go}} @label="hi" class="btn" />
 </template>
 ```
 
 ```gjs
 <template>
-  <button class="btn" role="button" aria-label="Submit">Send</button>
+  <div class="container" id="main" {{on "click" this.handleClick}}></div>
 </template>
 ```
 
-## Configuration
+## Options
 
-You can customize the order by providing an `order` array:
+| Name          | Type       | Default                                    | Description                                                                                                                  |
+| ------------- | ---------- | ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
+| `order`       | `string[]` | `["arguments", "attributes", "modifiers"]` | The order of token type groups. Valid values: `"arguments"`, `"attributes"`, `"modifiers"`, `"splattributes"`, `"comments"`. |
+| `alphabetize` | `boolean`  | `true`                                     | Whether to alphabetize attributes within each group.                                                                         |
 
 ```js
 module.exports = {
   rules: {
     'ember/template-attribute-order': [
       'error',
       {
-        order: ['class', 'id', 'role', 'aria-', 'type'],
+        order: ['arguments', 'attributes', 'modifiers'],
+        alphabetize: true,
       },
     ],
   },
@@ -68,4 +75,4 @@ module.exports = {
 
 ## References
 
-- [ember-template-lint attribute-order](https://github.com/ember-template-lint/ember-template-lint/blob/master/docs/rule/attribute-order.md)
+- [eslint-plugin-ember template-attribute-order](https://github.com/ember-cli/eslint-plugin-ember/blob/master/docs/rules/template-attribute-order.md)

docs/rules/no-restricted-service-injections.md

@@ -2,8 +2,6 @@
 
 <!-- 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
@@ -32,34 +30,34 @@ other attributes or builtin components.
 
 This rule **forbids** the following:
 
-```hbs
-<Input type='text' size='10' />
+```gjs
+<template><Input type='text' size='10' /></template>
 ```
 
-```hbs
-<Input @type='checkbox' checked />
+```gjs
+<template><Input @type='checkbox' checked /></template>
 ```
 
-```hbs
-<Textarea value="Hello, Tom!" /></Textarea>
+```gjs
+<template><Textarea value="Hello, Tom!" /></Textarea></template>
 ```
 
 This rule **allows** the following:
 
-```hbs
-<input type='text' size='10' />
+```gjs
+<template><input type='text' size='10' /></template>
 ```
 
-```hbs
-<Input @type='text' size='10' />
+```gjs
+<template><Input @type='text' size='10' /></template>
 ```
 
-```hbs
-<Input @type='checkbox' @checked={{true}} />
+```gjs
+<template><Input @type='checkbox' @checked={{true}} /></template>
 ```
 
-```hbs
-<Textarea @value="Hello, Tom!" /></Textarea>
+```gjs
+<template><Textarea @value="Hello, Tom!" /></Textarea></template>
 ```
 
 ## Migration

docs/rules/template-attribute-order.md

@@ -0,0 +1,37 @@
+# ember/template-deprecated-inline-view-helper
+
+<!-- end auto-generated rule header -->
+
+In Ember 1.12, support for invoking the inline View helper was deprecated.
+
+## Rule Details
+
+This rule flags `{{view}}` mustache or block statements that have hash pair arguments (e.g., `{{view 'foo' key=value}}`). Simple `{{view.property}}` path expressions or other usages without hash pairs are not flagged.
+
+## Examples
+
+This rule **forbids** the following:
+
+```gjs
+<template>
+  {{view 'this-is-bad' tagName="span"}}
+
+  {{#view tagName="span"}}content{{/view}}
+</template>
+```
+
+This rule **allows** the following:
+
+```gjs
+<template>
+  {{this-is-better}}
+
+  {{qux-qaz this=good}}
+
+  <div foo={{bar}}></div>
+</template>
+```
+
+## References
+
+- More information is available at the [Deprecation Guide](http://emberjs.com/deprecations/v1.x/#toc_ember-view).