Ghost/ghost/admin/app/components/gh-alerts.js

import Component from '@ember/component';
import {alias} from '@ember/object/computed';
import {inject as service} from '@ember/service';

export default Component.extend({
    tagName: 'aside',
    classNames: 'gh-alerts',

    notifications: service(),

    messages: alias('notifications.alerts')
});
Switched from ember-cli-shims to new module imports (#779) no issue - add eslint-plugin-ember, configure no-old-shims rule - run `eslint --fix` on `app`, `lib`, `mirage`, and `tests` to move imports to the new module imports - further cleanup of Ember globals usage - remove event-dispatcher initializer now that `canDispatchToEventManager` is deprecated 2017-08-22 10:53:26 +03:00			`import Component from '@ember/component';`
			`import {alias} from '@ember/object/computed';`
Match service/controller import to ember-modules-codemod style for consistency no issue Automated tools, code generators, and editor integrations are increasingly standardising on the import style used in `ember-modules-codemod`. Our import style differed a little with regards to service/controller injection imports which meant we were starting to see inconsistent naming. 2017-10-30 12:38:01 +03:00			`import {inject as service} from '@ember/service';`
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 14:36:45 +03:00
			`export default Component.extend({`
fixed notification components 2015-05-21 20:03:24 +03:00			`tagName: 'aside',`
			`classNames: 'gh-alerts',`

Match service/controller import to ember-modules-codemod style for consistency no issue Automated tools, code generators, and editor integrations are increasingly standardising on the import style used in `ember-modules-codemod`. Our import style differed a little with regards to service/controller injection imports which meant we were starting to see inconsistent naming. 2017-10-30 12:38:01 +03:00			`notifications: service(),`
fixed notification components 2015-05-21 20:03:24 +03:00
Remove unused top notification count functionality no issue - in a very old iteration of the admin design we needed a data attribute containing the number of notifications in order to add extra spacing in the styles. This hasn't been necessary for a long time and there are easier ways to do it now than using observers. 2017-11-24 13:47:06 +03:00			`messages: alias('notifications.alerts')`
fixed notification components 2015-05-21 20:03:24 +03:00			`});`