Fix CI: markdown linting, test failures in template-no-invalid-meta (127 rules ported)

Copilot · NullVoxPopuli · Copilot · commit 4638851059d0 · 2026-01-29T05:19:03.000Z
Co-authored-by: NullVoxPopuli &lt;199018+NullVoxPopuli@users.noreply.github.com&gt;
diff --git a/docs/rules/template-eol-last.md b/docs/rules/template-eol-last.md
@@ -55,6 +55,7 @@ Examples of **correct** code for this rule with `"never"` option:
 ## Configuration
 
 This rule takes one option:
+
 - `"always"` (default): requires a newline at the end
 - `"never"`: disallows a newline at the end
 
diff --git a/docs/rules/template-link-href-attributes.md b/docs/rules/template-link-href-attributes.md
@@ -56,6 +56,6 @@ Examples of **correct** code for this rule:
 
 ## References
 
-- [MDN: <a> - The Anchor element](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a)
+- [MDN: The Anchor element](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a)
 - [WebAIM: Links and Hypertext](https://webaim.org/techniques/hypertext/)
 - [ember-template-lint link-href-attributes](https://github.com/ember-template-lint/ember-template-lint/blob/master/docs/rule/link-href-attributes.md)
diff --git a/docs/rules/template-no-array-prototype-extensions.md b/docs/rules/template-no-array-prototype-extensions.md
@@ -13,6 +13,7 @@ Ember historically provided Array prototype extensions like `firstObject` and `l
 ## Rule Details
 
 This rule disallows using Ember Array prototype extensions in templates:
+
 - `firstObject`
 - `lastObject`
 - `@each`
diff --git a/docs/rules/template-no-bare-strings.md b/docs/rules/template-no-bare-strings.md
@@ -13,6 +13,7 @@ Bare strings in templates make internationalization (i18n) difficult. This rule
 This rule disallows text content in templates that isn't wrapped in a translation helper or passed as a property.
 
 The following are allowed:
+
 - Whitespace-only strings
 - Strings containing only numbers and punctuation
 - Strings in an allowlist (configurable)
diff --git a/docs/rules/template-no-down-event-binding.md b/docs/rules/template-no-down-event-binding.md
@@ -57,16 +57,19 @@ Examples of **correct** code for this rule:
 ## Migration
 
 Replace:
+
 ```gjs
 <button {{on "mousedown" this.action}}>
 ```
 
 With:
+
 ```gjs
 <button {{on "click" this.action}}>
 ```
 
 Or for keyboard support:
+
 ```gjs
 <button {{on "click" this.action}} {{on "keydown" this.handleKey}}>
 ```
diff --git a/docs/rules/template-no-duplicate-landmark-elements.md b/docs/rules/template-no-duplicate-landmark-elements.md
@@ -13,6 +13,7 @@ HTML5 landmark elements (like `<nav>`, `<header>`, `<footer>`, etc.) help screen
 This rule ensures that when multiple landmark elements of the same type appear in a template, each has a unique `aria-label` or `aria-labelledby` attribute.
 
 Landmark elements checked:
+
 - `header`
 - `footer`
 - `main`
diff --git a/docs/rules/template-no-form-action.md b/docs/rules/template-no-form-action.md
@@ -53,11 +53,13 @@ Examples of **correct** code for this rule:
 ## Migration
 
 Replace:
+
 ```gjs
 <form action="/submit">
 ```
 
 With:
+
 ```gjs
 <form {{on "submit" this.handleSubmit}}>
 ```
diff --git a/docs/rules/template-no-inline-event-handlers.md b/docs/rules/template-no-inline-event-handlers.md
@@ -57,11 +57,13 @@ Examples of **correct** code for this rule:
 ## Migration
 
 Replace:
+
 ```gjs
 <button onclick="alert('clicked')">
 ```
 
 With:
+
 ```gjs
 <button {{on "click" this.handleClick}}>
 ```
diff --git a/docs/rules/template-no-invalid-link-text.md b/docs/rules/template-no-invalid-link-text.md
@@ -11,6 +11,7 @@ Link text should be descriptive and provide context about the destination. Gener
 ## Rule Details
 
 This rule disallows the following link text values:
+
 - "click here"
 - "here"
 - "link"
diff --git a/docs/rules/template-no-multiple-empty-lines.md b/docs/rules/template-no-multiple-empty-lines.md
@@ -12,6 +12,10 @@ Multiple consecutive blank lines reduce readability and should be limited.
 
 This rule enforces a maximum number of consecutive empty lines (default: 1).
 
+## Config
+
+This rule has no configuration options.
+
 ## Examples
 
 Examples of **incorrect** code for this rule:
diff --git a/docs/rules/template-no-nested-interactive.md b/docs/rules/template-no-nested-interactive.md
@@ -13,6 +13,7 @@ Nested interactive elements (like a button inside a link) are not accessible to
 This rule disallows nesting interactive elements inside other interactive elements.
 
 Interactive elements include:
+
 - `<a>`
 - `<button>`
 - `<details>`
diff --git a/docs/rules/template-no-nested-landmark.md b/docs/rules/template-no-nested-landmark.md
@@ -13,6 +13,7 @@ Landmark elements should not be nested within other landmarks. This creates conf
 This rule disallows nesting landmark elements or roles within other landmark elements or roles.
 
 Landmark elements include:
+
 - `<header>` (banner)
 - `<nav>` (navigation)
 - `<main>` (main)
diff --git a/docs/rules/template-no-passed-in-event-handlers.md b/docs/rules/template-no-passed-in-event-handlers.md
@@ -57,11 +57,13 @@ Examples of **correct** code for this rule:
 ## Migration
 
 Replace:
+
 ```gjs
 <MyComponent @onClick={{this.handleClick}} />
 ```
 
 With:
+
 ```gjs
 <MyComponent>
   <button {{on "click" this.handleClick}}>Click</button>
diff --git a/docs/rules/template-no-pointer-down-event-binding.md b/docs/rules/template-no-pointer-down-event-binding.md
@@ -51,16 +51,19 @@ Examples of **correct** code for this rule:
 ## Migration
 
 Replace:
+
 ```gjs
 <button {{on "pointerdown" this.action}}>
 ```
 
 With:
+
 ```gjs
 <button {{on "click" this.action}}>
 ```
 
 Or for keyboard support:
+
 ```gjs
 <button {{on "click" this.action}} {{on "keydown" this.handleKey}}>
 ```
diff --git a/docs/rules/template-no-redundant-fn.md b/docs/rules/template-no-redundant-fn.md
@@ -51,11 +51,13 @@ Examples of **correct** code for this rule:
 ## Migration
 
 Replace:
+
 ```gjs
 <button {{on "click" (fn this.action)}}>
 ```
 
 With:
+
 ```gjs
 <button {{on "click" this.action}}>
 ```
diff --git a/docs/rules/template-no-redundant-landmark-role.md b/docs/rules/template-no-redundant-landmark-role.md
@@ -15,6 +15,7 @@ HTML5 semantic elements like `<nav>`, `<main>`, and `<aside>` have implicit ARIA
 This rule disallows adding explicit `role` attributes when the element already has that role implicitly.
 
 Implicit landmark roles:
+
 - `<header>` → `role="banner"` (when not nested in `<article>` or `<section>`)
 - `<footer>` → `role="contentinfo"` (when not nested in `<article>` or `<section>`)
 - `<nav>` → `role="navigation"`
diff --git a/docs/rules/template-no-route-action.md b/docs/rules/template-no-route-action.md
@@ -57,11 +57,13 @@ Examples of **correct** code for this rule:
 ## Migration
 
 Replace:
+
 ```gjs
 <button {{on "click" (route-action "save" model)}}>Save</button>
 ```
 
 With:
+
 ```gjs
 <button {{on "click" (fn this.save model)}}>Save</button>
 ```
diff --git a/docs/rules/template-require-context-role.md b/docs/rules/template-require-context-role.md
@@ -13,6 +13,7 @@ Some ARIA roles must be contained within specific parent roles to be meaningful
 This rule checks that context-dependent ARIA roles are used within the appropriate parent roles.
 
 Roles requiring context:
+
 - `listitem` → must be in `list`
 - `option` → must be in `listbox`
 - `tab` → must be in `tablist`
diff --git a/docs/rules/template-require-mandatory-role-attributes.md b/docs/rules/template-require-mandatory-role-attributes.md
@@ -13,6 +13,7 @@ Certain ARIA roles require specific attributes to be present for the role to be
 This rule checks that elements with ARIA roles include all required ARIA attributes for that role.
 
 Required attributes by role:
+
 - `checkbox`: requires `aria-checked`
 - `radio`: requires `aria-checked`
 - `slider`: requires `aria-valuenow`, `aria-valuemin`, `aria-valuemax`
diff --git a/docs/rules/template-style-concatenation.md b/docs/rules/template-style-concatenation.md
@@ -51,6 +51,7 @@ Examples of **correct** code for this rule:
 ## Migration
 
 In your component:
+
 ```js
 import { htmlSafe } from '@ember/template';
 
@@ -62,6 +63,7 @@ export default class MyComponent extends Component {
 ```
 
 Then in template:
+
 ```gjs
 <template>
   <div style={{this.computedStyle}}>Content</div>
diff --git a/lib/rules/template-no-invalid-meta.js b/lib/rules/template-no-invalid-meta.js
@@ -45,7 +45,7 @@ module.exports = {
         // Check for invalid charset value
         if (hasCharset && charsetValue) {
           const lowerCharset = charsetValue.toLowerCase();
-          if (lowerCharset !== 'utf8' && lowerCharset !== 'utf8') {
+          if (lowerCharset !== 'utf8' && lowerCharset !== 'utf-8') {
             context.report({
               node,
               messageId: 'invalidCharset',
