Skip to content
This repository has been archived by the owner on Mar 22, 2019. It is now read-only.

Module Transition #2339

Closed
wycats opened this issue Aug 20, 2015 · 2 comments
Closed

Module Transition #2339

wycats opened this issue Aug 20, 2015 · 2 comments

Comments

@wycats
Copy link
Member

wycats commented Aug 20, 2015

At some point in the future, we are going to want to support:

import Component from "ember/component";

in addition to the current:

import Ember from "ember";
var Component = Ember.Component;

We need the API docs to organize code around modules, but we also want to make sure that we keep around an up-to-date version of the docs (for 2.x) that organizes things around Ember.*.

The important thing is that people do not feel the ground shift out from under them when we start supporting the module form.

@SaladFork
Copy link
Contributor

Related, easing the transition by automating as much of it as possible: abuiles/ember-watson#13

@wifelette
Copy link
Member

Thanks so much for this. Alas, wrong repo :p This belongs here: https://github.com/emberjs/ember.js/issues

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants