Ghost/ghost/admin/app/components/gh-editor-post-status.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

39 lines
1.1 KiB
JavaScript

import Component from 'ember-component';
import computed, {reads} from 'ember-computed';
import {task, timeout} from 'ember-concurrency';
// TODO: reduce when in testing mode
const SAVE_TIMEOUT_MS = 3000;
export default Component.extend({
post: null,
isScheduled: reads('post.isScheduled'),
isSaving: false,
'data-test-editor-post-status': true,
_isSaving: false,
isPublished: computed('post.{isPublished,pastScheduledTime}', function () {
let isPublished = this.get('post.isPublished');
let pastScheduledTime = this.get('post.pastScheduledTime');
return isPublished || pastScheduledTime;
}),
// isSaving will only be true briefly whilst the post is saving,
// we want to ensure that the "Saving..." message is shown for at least
// a few seconds so that it's noticeable
didReceiveAttrs() {
if (this.get('isSaving')) {
this.get('showSavingMessage').perform();
}
},
showSavingMessage: task(function* () {
this.set('_isSaving', true);
yield timeout(SAVE_TIMEOUT_MS);
this.set('_isSaving', false);
}).drop()
});