Ghost/ghost/admin/app/controllers/settings/apps/index.js

/* eslint-disable ghost/ember/alias-model-in-controller */
import Controller from '@ember/controller';
import {inject as service} from '@ember/service';

export default Controller.extend({
    settings: service()
});
ESLint: Alias model in controllers no issue - https://github.com/ember-cli/eslint-plugin-ember/blob/HEAD/docs/rules/alias-model-in-controller.md - replace `model` with a meaningful property name everywhere possible - refactor `design` and `general` settings controllers to use a directly injected settings service rather than passing it in as a "model" to be more explicit 2018-01-11 01:57:43 +03:00			`/* eslint-disable ghost/ember/alias-model-in-controller */`
🐛 Fixed "active" state of apps on apps index screen (#843) no issue On the apps index screen there were conditionals for each app so that active apps show "Active" instead of "Configure" when they are activated - the conditionals weren't working because the properties they check for weren't available in the template's context. - add a new `settings/apps/index` controller that imports the `settings` service - updates template conditionals to check for properties on the `settings` service 2017-08-30 15:31:04 +03:00			`import Controller from '@ember/controller';`
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';`
🐛 Fixed "active" state of apps on apps index screen (#843) no issue On the apps index screen there were conditionals for each app so that active apps show "Active" instead of "Configure" when they are activated - the conditionals weren't working because the properties they check for weren't available in the template's context. - add a new `settings/apps/index` controller that imports the `settings` service - updates template conditionals to check for properties on the `settings` service 2017-08-30 15:31:04 +03:00
			`export default Controller.extend({`
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			`settings: service()`
🐛 Fixed "active" state of apps on apps index screen (#843) no issue On the apps index screen there were conditionals for each app so that active apps show "Active" instead of "Configure" when they are activated - the conditionals weren't working because the properties they check for weren't available in the template's context. - add a new `settings/apps/index` controller that imports the `settings` service - updates template conditionals to check for properties on the `settings` service 2017-08-30 15:31:04 +03:00			`});`