chriskrycho
commented
2 years ago - Thanks to @ventuno, we have ember-template-lint support!
- Thanks to @gitKrystan, we have Prettier support!
- Thanks to @NullVoxPopuli and @nlfurniss, we have ESLint support!
Thanks as well to @wycats, @bmish, and @rwjblue for helping get those various efforts across the line.
I’ll make sure we follow up on this in one of the next few Framework Core team meetings—this is amazing progress, and represents a huge step toward stabilizing this and eventually making it the recommended way of writing Ember templates.
(Keep your eyes open for code-mods coming soon™!)
ef4
wagenet
NullVoxPopuli
Windvis
The path to making RFC emberjs/ember.js#779: First-Class Component Templates stable and recommended for end users.
What even is this?
## Background [RFC emberjs/ember.js#779: First-Class Component Templates][fccts] picked `` tags as the the ability for Ember (and Glimmer) developers to write components with `template` tags embedded in their JS, like so: ```js import Component from '@glimmer/component'; const Button = export default class Player extends Component { @tracked isPlaying = false; play = () => (this.isPlaying = true); pause = () => (this.isPlaying = false); } ``` This is not only a general win for ease of working with Ember: it is also a key part of our TypeScript story, because it makes things like go-to-definition, documentation hovers, autocomplete, auto-import, etc. all *much* easier to manage. So: what do we need to do to finish unblocking its adoption?The Road to Stable
See ember-template-imports/ember-template-imports#35 for details on each part of this.
The Road to Recommended
ember-template-importsember-template-importsinto Glimmer, with Ember being a customer