cb59388c5b
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.
25 lines
787 B
JavaScript
25 lines
787 B
JavaScript
import hbs from 'htmlbars-inline-precompile';
|
|
import {describe, it} from 'mocha';
|
|
import {expect} from 'chai';
|
|
import {setupComponentTest} from 'ember-mocha';
|
|
|
|
describe('Integration: Component: gh-date-time-picker', function() {
|
|
setupComponentTest('gh-date-time-picker', {
|
|
integration: true
|
|
});
|
|
|
|
it.skip('renders', function() {
|
|
// Set any properties with this.set('myProperty', 'value');
|
|
// Handle any actions with this.on('myAction', function(val) { ... });
|
|
// Template block usage:
|
|
// this.render(hbs`
|
|
// {{#gh-date-time-picker}}
|
|
// template content
|
|
// {{/gh-date-time-picker}}
|
|
// `);
|
|
|
|
this.render(hbs`{{gh-date-time-picker}}`);
|
|
expect(this.$()).to.have.length(1);
|
|
});
|
|
});
|