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

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

export default Component.extend({
    notifications: service(),

    tagName: 'aside',
    classNames: 'gh-notifications',

    messages: alias('notifications.notifications')
});
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({`
ESLint: Consistent ember property/method ordering no issue - https://github.com/ember-cli/eslint-plugin-ember/blob/master/docs/rules/order-in-components.md - https://github.com/ember-cli/eslint-plugin-ember/blob/master/docs/rules/order-in-controllers.md - https://github.com/ember-cli/eslint-plugin-ember/blob/master/docs/rules/order-in-routes.md 2018-01-11 20:43:23 +03:00			`notifications: service(),`

Implement Notifications for Ember closes #2417 - Adds Notification(s)Component - Render notifications in application.hbs - Adds handleError in application route 2014-03-22 16:08:15 +04:00			`tagName: 'aside',`
fixed notification components 2015-05-21 20:03:24 +03:00			`classNames: 'gh-notifications',`
Turn on update notifications for Ember admin Issue #3160 - Use notifications API to display available update notification. - Remove update_notification handlebars helper as now both the check for an available update and the notification handling is run from the server's admin controller index method. - Bind the notification's location property to a css class for styling. - Refactor Ember notifications to better handle notification objects. Move responsibility for css class generation onto the notification component. - Refactor gh-notifications component to take a location argument that's used to assign a css class and filter notifications. 2014-07-09 08:17:30 +04:00
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			`messages: alias('notifications.notifications')`
Implement Notifications for Ember closes #2417 - Adds Notification(s)Component - Render notifications in application.hbs - Adds handleError in application route 2014-03-22 16:08:15 +04:00			`});`