[import-order] order within `import type`

[alvis]

Now, import type can be a separate group.
I also find the ability to alphabetize very useful.

However, I find it very annoying that they don't work well together.
The problem is that the order of import type statement doesn't follow the order we define for other module types.
Let's say we have the following options

"import/order": [
  "warn",
  {
    "groups": [
      "builtin",
      "external",
      "type"
    ],
    "newlines-between": "always-and-inside-groups",
    "alphabetize": { "order": "asc", "caseInsensitive": true }
  }
],

e.g. I'd like to have the following order

// buildin modules before external modules

// for ordinary import it's ok, builtin first, then external
import { createServer } from 'http'

import { graphql } from 'gatsby';

// but for `import type` it warns that the gatsby import should be put in front of the http one
// the order is right here since http is a buildin and gatsby is an external
import type { RequestOptions } from 'http'

import type { PageProps } from 'gatsby';

[ljharb]

Seems like to do what you want, the schema would need some way of providing alternative config options for a specific group.

I suppose we could add groupOverrides: { [groupName]: groupConfiguration }, but that seems like a lot of complexity for such a specific use case.

[alvis]

or can we take the order from groups excluding type when we analyze the order within import type statements?

[ljharb]

I'm not sure what you mean. Can you elaborate?

[Exelenz9]

This answer helped me to solve similar problem

[kaysonwu]

I have the same issue. @ljharb the type group should also follow the basic order, e.g. : "builtin", "external", "internal", "parent", "Sibling ","index", "object"

[danranVm]

I have the same problem.

import type { TablePagination, TableProps } from '../types'
import type { TableConfig } from '@idux/components/config'
import type { ComputedRef } from 'vue'

import { computed, ref, watchEffect } from 'vue'

import { callEmit } from '@idux/cdk/utils'
import { useGlobalConfig } from '@idux/components/config'

import { tablePagination, tableProps } from '../types'

my config :

          {
            alphabetize: { order: 'asc', caseInsensitive: false },
            'newlines-between': 'always',
            groups: ['type', 'builtin', 'external', 'internal', ['parent', 'sibling', 'index']],
            pathGroups: [
              {
                pattern: '{vue,@vue/**}',
                group: 'external',
                position: 'before',
              },
              {
                pattern: '@idux/**',
                group: 'internal',
                position: 'before',
              },
            ],
            pathGroupsExcludedImportTypes: ['type'],
          },

[danranVm]

Seems like to do what you want, the schema would need some way of providing alternative config options for a specific group.

I suppose we could add , but that seems like a lot of complexity for such a specific use case.groupOverrides: { [groupName]: groupConfiguration }

Hope to support this configuration, thank you.

@ljharb In addition, I have another idea, for 'type' grouping, according to groups' exclude 'type', do a sort again.