sort-imports should treat single import of multiple style as "multiple" type

What version of ESLint are you using? HEAD

What rule do you want to change? sort-imports

What code should no longer be flagged as incorrect with this change?

import * as bar from 'bar.js';
import { a } from 'foo';

What happens when the rule is applied to this code now? X:Y error Imports should be sorted alphabetically

Root cause The rule uses node.specifiers.length to determine if an import is of type multiple or single. The bug is that imports of multiple-style with a single import (import { a } from 'foo';) are treated as single.

[btmills]

@LegNeato thanks for your patience and for putting together that repro. I’m getting the same results now.

Before I consider the bug verified and accept the issue, are we comfortable treating the “single” option as a synonym for default imports and the “multiple” option as a synonym for named imports?

If accepted as stated, this would be a semver-minor change, as it could result in more errors in the following case:

// test6736_reversed.js
import { a } from 'foo'; // Multiple
import bar from 'bar.js'; // Single

Currently, the above case does not error. After this change, it would warn.

[kaicataldo]

I’m closing this issue because it looks like consensus couldn’t be reached. While we wish we could accommodate all requests, we have limited resources and do need to prioritize. We’ve found that issues failing to reach consensus after 21 days tend to never reach consensus, and as a team have decided to close such issues. This doesn’t mean the idea isn’t interesting or valuable, only that it’s not something the team can commit to at the moment.