Tips for staying on top of imports

@erikrothoff wrote:

The “new” way of importing Ember components is cool and all, but the multi-levelness of it is really hard to grasp. Previously the computed decorator was simply Ember.computed, now it’s in @ember/object. Other decorators like alias are nested even further in @ember/object/computed.

Component is in @ember/component but to create helpers you now import { helper } from '@ember/component/helper'. Ember.run.later is now as import { later } from '@ember/runloop', Ember.Route is now all the way in @ember/routing/route.

These are just some examples off the top of my head. Now my intention is not to argue about the module design of Ember, I’m just wanting to adapt. It used to be really easy to remember where everything was as it was simply on the Ember namespace object.

I’m using Atom so not getting much help from my editor to auto-import anything. Is there a plugin for this? Did anyone else feel this pain when migrating, or am I just slow to catch on?

Posts: 1

Participants: 1

Read full topic