Skip to content

Commit

Permalink
Update 1046-template-tag-in-routes.md
Browse files Browse the repository at this point in the history
typo fixes
  • Loading branch information
ANordmoe authored Mar 3, 2025
1 parent c249bed commit 7a8ec31
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions text/1046-template-tag-in-routes.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ suite: Leave as is

## Summary

Allow `app/templates/*.hbs` to convert to `app/temlates/*.gjs`.
Allow `app/templates/*.hbs` to convert to `app/templates/*.gjs`.

## Motivation

Expand Down Expand Up @@ -161,7 +161,7 @@ No new typescript-specific features are required. If you're authoring route temp

This RFC was directly inspired by a first attempt at updating the Guides for Template Tag. It became immediately apparent that we can write _much_ clearer guides if we can teach all GJS, instead of a mix of GJS and HBS.

Starting at https://guides.emberjs.com/release/components/ when the first `application.hbs` file is introduced, we would use `.gjs` instead. In those opening examples that are empahsizing HTML, the only change to the content would be wrapping `<template></template>` around the HTML.
Starting at https://guides.emberjs.com/release/components/ when the first `application.hbs` file is introduced, we would use `.gjs` instead. In those opening examples that are emphasizing HTML, the only change to the content would be wrapping `<template></template>` around the HTML.

Progressing to https://guides.emberjs.com/release/components/introducing-components/, learners extract their first component. It now becomes possible to do that within the same file. This allows teaching fewer things in a single step. First, people can learn what a component is. Second, it can be refactored into a separate file. We can avoid teaching anything about "pascal case" and naming rules, because everything just follows javascript naming rules.

Expand Down

0 comments on commit 7a8ec31

Please sign in to comment.