sort-imports: support ordering relative imports vs package imports

Proposal

Either extend the existing sort-imports rule, or create a new rule which will enforce ordering / separation of relative imports vs package imports.

This is a stylistic rule and provides developer the means to keep clear separation between groups of imports helping visually seperate external dependencies (eg: React) from internal code.

Good

import moment from 'moment';
import React, { PropTypes } from 'react';
import styles from './ArchiveDetails.css';
import { SHOWN, HIDDEN } from '../actions/error';

Bad

import moment from 'moment';
import styles from './ArchiveDetails.css';
import React, { PropTypes } from 'react';
import { SHOWN, HIDDEN } from '../actions/error';

Why the rule should be in the core instead of creating a custom rule.

Feel like a logical extension of the sort-imports rule; although happy to be informed otherwise.

Are you willing to create the rule yourself?

Possibly; although I don’t have a lot of free time to dedicate to the cause 😦

[verekia]

For those who are wondering how to combine eslint-plugin-import with alphabetical order like sort-import does, this is not possible yet with the plugin. An issue is open on the plugin as a feature suggestion. So unfortunately, we can’t currently both lint for alphabetical order and import type (absolute/relative).

[ilyavolodin]

Re-reading this issue. I think this should go into eslint-plugin-import instead of the core. And it seem this rule already exists there. @eslint/eslint-team anyone feels differently?