Ghost/ghost/admin/app/app.js
Kevin Ansfield cb59388c5b 💄🐷 sort-imports eslint rule (#712)
no issue

- adds `eslint-plugin-sort-imports-es6-autofix` dependency
  - implements ESLint's base `sort-imports` rule but has a distinction in that `import {foo} from 'bar';` is considered `multiple` rather than `single`
  - fixes ESLint's autofix behaviour so `eslint --fix` will actually fix the sort order
- updates all unordered import rules by using `eslint --fix`

With the increased number of `import` statements since Ember+ecosystem started moving towards es6 modules I've found it frustrating at times trying to search through randomly ordered import statements. Recently I've been sorting imports manually when I've added new code or touched old code so I thought I'd add an ESLint rule to codify it.
2017-05-29 20:50:03 +02:00

44 lines
1.0 KiB
JavaScript
Executable File

import 'ghost-admin/utils/link-component';
import 'ghost-admin/utils/route';
import 'ghost-admin/utils/text-field';
import Application from 'ember-application';
import Ember from 'ember';
import Resolver from './resolver';
import config from './config/environment';
import loadInitializers from 'ember-load-initializers';
Ember.MODEL_FACTORY_INJECTIONS = true;
let App = Application.extend({
Resolver,
modulePrefix: config.modulePrefix,
podModulePrefix: config.podModulePrefix,
customEvents: {
touchstart: null,
touchmove: null,
touchend: null,
touchcancel: null
}
});
// TODO: remove once the validations refactor is complete
// eslint-disable-next-line
Ember.Debug.registerWarnHandler((message, options, next) => {
let skip = [
'ds.errors.add',
'ds.errors.remove',
'ds.errors.clear'
];
if (skip.includes(options.id)) {
return;
}
next(message, options);
});
loadInitializers(App, config.modulePrefix);
export default App;