Skip to content

fix: Set import/order groups explicitly

Vitaly Slobodin requested to merge vs-explicitly-set-import-order into master

Apparently default configuration of the rule import/order does now know anything about aliases paths (~ or ee_else_ce) in webpack. That leads to improper order of imports in JavaScript files:

import * as types from './mutation_types';
import ceMutations from '~/vue_shared/security_reports/store/modules/sast/mutations';
import { findIssueIndex } from '../../utils';

The line import * as types from './mutation_types'; must go after import ceMutations because this is a relative import.

Thanks to @markrian for finding this! 🚀

Merge request reports