I feel this construct is outdated in the age of ember-cli
that automatically put your add-ons in an add-on namespace.
Is there a case where Ember.Namespace
is still needed?
I feel this construct is outdated in the age of ember-cli
that automatically put your add-ons in an add-on namespace.
Is there a case where Ember.Namespace
is still needed?
It is still used. See: https://gist.github.com/jayphelps/8432362
I don’t think what’s written in the gist is really applicable as it is written over a year ago. It doesn’t show modules written as ES6 modules.
ember-cli
automatically compiles apps under an AMD module namespace. You can extract shared code as add-ons if you’re just looking for code reuse. The add-ons are automatically compiled under a different AMD module namespace.
So if codes are already namespaced by AMD modules, why do we still need Ember.Namespace
?