From 88854a5c73a4bf199da10b700bded2dba362a8e0 Mon Sep 17 00:00:00 2001
From: Tony Miller <mcfiredrill@gmail.com>
Date: Thu, 23 Oct 2025 12:22:41 -0700
Subject: [PATCH 1/4] use gjs in Linking Between Routes guide

Changed the templates from .hbs to .gjs, and added relevant imports.

I didn't add the import or <template> when it looked like the example was only showing part of a template.
---
 .../release/routing/linking-between-routes.md | 93 +++++++++++--------
 1 file changed, 54 insertions(+), 39 deletions(-)

diff --git a/guides/release/routing/linking-between-routes.md b/guides/release/routing/linking-between-routes.md
index f422c27473..0bb573cca9 100644
--- a/guides/release/routing/linking-between-routes.md
+++ b/guides/release/routing/linking-between-routes.md
@@ -16,14 +16,17 @@ Router.map(function() {
 });
 ```
 
-```handlebars {data-filename=app/templates/photos.hbs}
-<ul>
-  {{#each this.photos as |p|}}
-    <li>
-      <LinkTo @route="photos.edit" @model={{p}}>{{p.title}}</LinkTo>
-    </li>
-  {{/each}}
-</ul>
+```handlebars {data-filename=app/templates/photos.gjs}
+import { LinkTo } from '@ember/routing';
+<template>
+  <ul>
+    {{#each this.photos as |p|}}
+      <li>
+        <LinkTo @route="photos.edit" @model={{p}}>{{p.title}}</LinkTo>
+      </li>
+    {{/each}}
+  </ul>
+</template>
 ```
 
 The `@route` argument is the name of the route to link to, and the `@model`
@@ -56,7 +59,7 @@ behavior can be customized within `PhotoEditRoute`'s `serialize` hook.
 Alternatively, you can explicitly provide a serialized `id`, in place of
 passing a model object:
 
-```handlebars {data-filename=app/templates/photos.hbs}
+```handlebars {data-filename=app/templates/photos.gjs}
 <LinkTo @route="photos.edit" @model="1">First Photo Ever</LinkTo>
 ```
 
@@ -93,14 +96,17 @@ will be given the `active` CSS class. For example, if you were at the URL
 
 The CSS class name used for active classes can be customized for a single use of `<LinkTo />` by passing an `@activeClass` argument:
 
-```handlebars {data-filename=app/templates/photos.hbs}
-<ul>
-  {{#each this.photos as |p|}}
-    <li>
-      <LinkTo @route="photos.edit" @model={{p}} @activeClass="font-bold">{{p.title}}</LinkTo>
-    </li>
-  {{/each}}
-</ul>
+```handlebars {data-filename=app/templates/photos.gjs}
+import { LinkTo } from '@ember/routing';
+<template>
+  <ul>
+    {{#each this.photos as |p|}}
+      <li>
+        <LinkTo @route="photos.edit" @model={{p}} @activeClass="font-bold">{{p.title}}</LinkTo>
+      </li>
+    {{/each}}
+  </ul>
+</template>
 ```
 
 will result in:
@@ -146,12 +152,15 @@ URL.
 
 For example, if we are currently on `/photos/2`, then the following template:
 
-```handlebars {data-filename=app/templates/photos/photo.hbs}
-{{#each this.photo.comments as |comment|}}
-  <LinkTo @route="photos.photo.comment" @model={{comment}}>
-    {{excerpt comment.body}}...
-  </LinkTo>
-{{/each}}
+```handlebars {data-filename=app/templates/photos/photo.gjs}
+import { LinkTo } from '@ember/routing';
+<template>
+  {{#each this.photo.comments as |comment|}}
+    <LinkTo @route="photos.photo.comment" @model={{comment}}>
+      {{excerpt comment.body}}...
+    </LinkTo>
+  {{/each}}
+</template>
 ```
 
 ...will render something like this:
@@ -182,18 +191,21 @@ To solve this problem, or maybe to cross-link comments from photos other than
 the currently active one, you can pass an array of model objects using the
 `@models` argument and the `{{array}}` helper:
 
-```handlebars {data-filename=app/templates/photos.hbs}
-<h1>Latest Comments</h1>
-
-<ul>
-  {{#each this.latestComments as |comment|}}
-    <li>
-      <LinkTo @route="photos.photo.comment" @models={{array comment.photo comment}}>
-        {{excerpt comment.body}}...
-      </LinkTo>
-    </li>
-  {{/each}}
-</ul>
+```handlebars {data-filename=app/templates/photos.gjs}
+import { LinkTo } from '@ember/routing';
+<template>
+  <h1>Latest Comments</h1>
+  
+  <ul>
+    {{#each this.latestComments as |comment|}}
+      <li>
+        <LinkTo @route="photos.photo.comment" @models={{array comment.photo comment}}>
+          {{excerpt comment.body}}...
+        </LinkTo>
+      </li>
+    {{/each}}
+  </ul>
+</template>
 ```
 
 Here, we are passing an array of model objects (the photo, then the comment),
@@ -224,10 +236,13 @@ example, it is quite common to want to add additional CSS classes to the
 generated link tag, or specifying the appropriate ARIA attributes. You can
 simply pass them along with the invocation:
 
-```handlebars {data-filename=app/templates/photos/edit.hbs}
-<LinkTo @route="photos" class="btn btn-primary" role="button" aria-pressed="false">
-  Discard Changes
-</LinkTo>
+```handlebars {data-filename=app/templates/photos/edit.gjs}
+import { LinkTo } from '@ember/routing';
+<template>  
+  <LinkTo @route="photos" class="btn btn-primary" role="button" aria-pressed="false">
+    Discard Changes
+  </LinkTo>
+</template>
 ```
 
 CSS classes passed this way will be _in addition to_ the standard `ember-view`

From 9eb2719585359abac5dd559c28ad5d758c5e2ec9 Mon Sep 17 00:00:00 2001
From: Tony Miller <mcfiredrill@gmail.com>
Date: Fri, 24 Oct 2025 10:37:27 -0700
Subject: [PATCH 2/4] update language on code blocks

---
 .../release/routing/linking-between-routes.md | 20 +++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/guides/release/routing/linking-between-routes.md b/guides/release/routing/linking-between-routes.md
index 0bb573cca9..3cff54c586 100644
--- a/guides/release/routing/linking-between-routes.md
+++ b/guides/release/routing/linking-between-routes.md
@@ -16,7 +16,7 @@ Router.map(function() {
 });
 ```
 
-```handlebars {data-filename=app/templates/photos.gjs}
+```gjs {data-filename=app/templates/photos.gjs}
 import { LinkTo } from '@ember/routing';
 <template>
   <ul>
@@ -59,7 +59,7 @@ behavior can be customized within `PhotoEditRoute`'s `serialize` hook.
 Alternatively, you can explicitly provide a serialized `id`, in place of
 passing a model object:
 
-```handlebars {data-filename=app/templates/photos.gjs}
+```gjs {data-filename=app/templates/photos.gjs}
 <LinkTo @route="photos.edit" @model="1">First Photo Ever</LinkTo>
 ```
 
@@ -96,7 +96,7 @@ will be given the `active` CSS class. For example, if you were at the URL
 
 The CSS class name used for active classes can be customized for a single use of `<LinkTo />` by passing an `@activeClass` argument:
 
-```handlebars {data-filename=app/templates/photos.gjs}
+```gjs {data-filename=app/templates/photos.gjs}
 import { LinkTo } from '@ember/routing';
 <template>
   <ul>
@@ -152,7 +152,7 @@ URL.
 
 For example, if we are currently on `/photos/2`, then the following template:
 
-```handlebars {data-filename=app/templates/photos/photo.gjs}
+```gjs {data-filename=app/templates/photos/photo.gjs}
 import { LinkTo } from '@ember/routing';
 <template>
   {{#each this.photo.comments as |comment|}}
@@ -191,11 +191,11 @@ To solve this problem, or maybe to cross-link comments from photos other than
 the currently active one, you can pass an array of model objects using the
 `@models` argument and the `{{array}}` helper:
 
-```handlebars {data-filename=app/templates/photos.gjs}
+```gjs {data-filename=app/templates/photos.gjs}
 import { LinkTo } from '@ember/routing';
 <template>
   <h1>Latest Comments</h1>
-  
+
   <ul>
     {{#each this.latestComments as |comment|}}
       <li>
@@ -219,7 +219,7 @@ argument. Therefore, it is an error to pass _both_ arguments at the same time.
 The `@query` argument, along with the `{{hash}}` helper, can be used to set
 query params on a link:
 
-```handlebars
+```gjs
 // Explicitly set target query params
 <LinkTo @route="posts" @query={{hash direction="asc"}}>Sort</LinkTo>
 
@@ -236,9 +236,9 @@ example, it is quite common to want to add additional CSS classes to the
 generated link tag, or specifying the appropriate ARIA attributes. You can
 simply pass them along with the invocation:
 
-```handlebars {data-filename=app/templates/photos/edit.gjs}
+```gjs {data-filename=app/templates/photos/edit.gjs}
 import { LinkTo } from '@ember/routing';
-<template>  
+<template>
   <LinkTo @route="photos" class="btn btn-primary" role="button" aria-pressed="false">
     Discard Changes
   </LinkTo>
@@ -255,7 +255,7 @@ browser's history when transitioning between routes. However, to replace the
 current entry in the browser's history instead, you can use the `@replace`
 option:
 
-```handlebars
+```gjs
 <LinkTo @route="photo.comment" @model={{this.topComment}} @replace={{true}}>
   Top comment for the current photo
 </Link>

From c2c7a2ac5eb7a8b75cdb34b6d173c8596bbde921 Mon Sep 17 00:00:00 2001
From: Tony Miller <mcfiredrill@gmail.com>
Date: Sun, 26 Oct 2025 09:49:29 -0700
Subject: [PATCH 3/4] use @controller in example

---
 guides/release/routing/linking-between-routes.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/guides/release/routing/linking-between-routes.md b/guides/release/routing/linking-between-routes.md
index 3cff54c586..7b1b16c07f 100644
--- a/guides/release/routing/linking-between-routes.md
+++ b/guides/release/routing/linking-between-routes.md
@@ -193,11 +193,12 @@ the currently active one, you can pass an array of model objects using the
 
 ```gjs {data-filename=app/templates/photos.gjs}
 import { LinkTo } from '@ember/routing';
+
 <template>
   <h1>Latest Comments</h1>
 
   <ul>
-    {{#each this.latestComments as |comment|}}
+    {{#each @controller.latestComments as |comment|}}
       <li>
         <LinkTo @route="photos.photo.comment" @models={{array comment.photo comment}}>
           {{excerpt comment.body}}...

From 8cda408e55bb4db36ae043149bb23130f9c1daea Mon Sep 17 00:00:00 2001
From: Tony Miller <mcfiredrill@gmail.com>
Date: Sun, 26 Oct 2025 10:03:31 -0700
Subject: [PATCH 4/4] use backing class

---
 guides/release/routing/linking-between-routes.md | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/guides/release/routing/linking-between-routes.md b/guides/release/routing/linking-between-routes.md
index 7b1b16c07f..744df6c6c4 100644
--- a/guides/release/routing/linking-between-routes.md
+++ b/guides/release/routing/linking-between-routes.md
@@ -193,12 +193,19 @@ the currently active one, you can pass an array of model objects using the
 
 ```gjs {data-filename=app/templates/photos.gjs}
 import { LinkTo } from '@ember/routing';
+import { array } from '@ember/helper';
+
+export default class {
+  get latestComments() {
+    return this.model.sort((a, b) => new Date(b.date) - new Date(a.date)).slice(0, 5);
+  }
+}
 
 <template>
   <h1>Latest Comments</h1>
 
   <ul>
-    {{#each @controller.latestComments as |comment|}}
+    {{#each this.latestComments as |comment|}}
       <li>
         <LinkTo @route="photos.photo.comment" @models={{array comment.photo comment}}>
           {{excerpt comment.body}}...