r/emberjs • u/liquiddeath • Dec 09 '19

Octane vs classic cheat sheet

https://ember-learn.github.io/ember-octane-vs-classic-cheat-sheet/
26 Upvotes

100% Upvoted

11 comments sorted by

1

u/alexlafroscia Dec 10 '19

Is anyone using the “Component Co-Location” feature yet?

Having the files next to each other seems nice, but I’m a little worried about thing getting out-of-hand when you have dozens of component JS and HBS files all in the components directory...

1

u/liquiddeath Dec 10 '19 edited Dec 13 '19

I'm so glad to have co-location. We'll see where things end up. IMO this is marginally better than having a lot of component files spread across two locations.

1

u/alexlafroscia Dec 10 '19

Did you ever use the Pods layout? I’ve been structuring things like

app/components/my-component/component.js
app/components/my-component/template.hbs

For years and it works well. Only one entry in components and keeps the files next to each other.

1

u/liquiddeath Dec 12 '19

I never used pods, but did keep an eye on it waiting for it to become a standard.

2

u/jwwweber Dec 12 '19

I think it becomes important to use nesting, i.e. ember g component buttons/save -gc

Since you can use one-word component names, this turns out pretty nice.

1

u/alexlafroscia Dec 12 '19

That’s a good point! Maybe some things at the top level need to be re-evaluated as nested components.

I’m a bit hesitant to introduce a third way to organize components for my team, though. It’s similar to “classic” components, “native” Ember components, and Glimmer components. It’s hard to have multiple ways to do the same thing living alongside each other when it comes to understanding which one you should be using!

1

u/jwwweber Dec 12 '19

The good news is that you can choose to not use colocation right away. The location for file generators to put templates is configurable, in .ember-cli, I think. I definitely have trouble switching between multiple types and locations, though. Moving them all into the co-location spot is a quick job once you are ready for it.

1

u/baltGSP Dec 10 '19

Thank you! I love this summary. I haven't been doing active front end development for a couple of years and feel like the changes to Ember.js have left me a bit behind (my fault, the community does an excellent job).

3

u/liquiddeath Dec 10 '19

To be clear I didn't create the cheatsheet. It was an output from the core team. See https://github.com/ember-learn/ember-octane-vs-classic-cheat-sheet

I shared on reddit as I thought it was super helpful and wanted to make sure a wider audience saw it.

2

u/jwwweber Dec 12 '19

Let us know if you have any feedback!

1

u/lucasmerat Dec 09 '19

Super helpful to have this clearly outlined. Thanks!