ghost/core/client/app/routes/setup/index.js

import Ember from 'ember';

const {Route} = Ember;

export default Route.extend({
    beforeModel() {
        this._super(...arguments);
        this.transitionTo('setup.one');
    }
});
First pass at user onboarding screens refs #5315 - split setup into 3 screens - add gravatar fetching - add download counter - add button handling for invite users 2015-03-29 20:10:53 +02:00			`import Ember from 'ember';`

Use es6 across client and add ember-suave to enforce rules no issue - add ember-suave dependency - upgrade grunt-jscs dependency - add a new .jscsrc for the client's tests directory that extends from client's base .jscsrc - separate client tests in Gruntfile jscs task so they pick up the test's .jscsrc - standardize es6 usage across client 2015-10-28 11:36:45 +00:00			`const {Route} = Ember;`

			`export default Route.extend({`
			`beforeModel() {`
Always call `_super` when using Ember hooks no issue - review use of Ember core hooks and add a call to `this._super` if missing - fix a few occurrences of using the wrong component lifecycle hooks that could result in multiple/duplicate event handlers being attached `_super` should always be called when overriding Ember's base hooks so that core functionality or app functionality added through extensions, mixins or addons is not lost. This is important as it guards against issues arising from later refactorings or core changes. As example of lost functionality, there were a number of routes that extended from `AuthenticatedRoute` but then overrode the `beforeModel` hook without calling `_super` which meant that the route was no longer treated as authenticated. 2015-11-15 11:06:49 +00:00			`this._super(...arguments);`
First pass at user onboarding screens refs #5315 - split setup into 3 screens - add gravatar fetching - add download counter - add button handling for invite users 2015-03-29 20:10:53 +02:00			`this.transitionTo('setup.one');`
			`}`
			`});`