Interest in adding "no-restricted-glob-paths" rule?

• no-restricted-paths doesn’t support globs.
• no-restricted-imports supports globs/git-ignore-like but just as strings, no path resolving support.

So if there is an interested I think I could PR the no-restricted-glob-paths rule. The functionality would be similar to https://github.com/vladimiry/tslint-rules-bunch.

I would prefer to use https://github.com/micromatch/picomatch module for globbing even though the minimatch module is already used. The reason is that picomatch is faster and supports arrays of patterns for both str / pattern arguments on ismatch(str, pattern) function call.

Proposed configuration schema (basePath props both on top/zone levels are optional):

schema: [{
  type: 'object',
  required: ["zones"],
  properties: {
    basePath: {type: ["string"]},
    zones: {
      type: "array",
      minItems: 1,
      items: {
        type: "object",
        required: ["target", "from"],
        properties: {
          basePath: {type: ["string"]},
          target: {
            anyOf: [
              {type: "string"},
              {type: "array", items: {type: "string"}},
            ],
          },
          from: {
            anyOf: [
              {type: "string"},
              {type: "array", items: {type: "string"}},
            ],
          },
        },
        additionalProperties: false,
      },
    },
  },
  additionalProperties: false
}]

Configuration example:

{
  "plugins": [
    "import"
  ],
  "settings": {
    "import/resolver": {
      "typescript": {}
    }
  },
  "rules": {
    "import/no-restricted-glob-paths": [
      "error",
      {
        "zones": [
          {
            "target": "src/electron-main/**/*",
            "from": [
              "./**/*",
              "!./node_modules/**/*",
              "!src/electron-main/**/*",
              "!src/shared/**/*"
            ]
          },
          {
            "basePath": "./src",
            "target": [
              "!./electron-main/database/entity/**/*",
              "!./electron-main/database/validation.ts"
            ],
            "from": [
              "./electron-main/database/entity",
              "./electron-main/database/entity/**/*"
            ]
          }
        ]
      }
    ]
  }
}

#1132 is a possibly related issue, CC @Bessonov

[vladimiry]

We could still add the glob support, and then plan to remove except in the future - they seem like they could coexist.

What if we make zones array to include second object type? So we keep existing zones object type and we change nothing in the respective logic. But we add a second object type and apply new logic with glob support for this object. If we go this way then there will be no breaking changes.

So the zones array type would look like:

interface Options {
    zones: Array<
        // currently supported options zone type
        | {
            target: string;
            from: string;
            except?: string[];
        }
        // new options zone type which gets new handling logic
        // that doesn't interfere with existing logic
        | {
            basePath?: string;
            targetGlob: string | string[];
            fromGlob: string | string[];
        }
    >;
}

[vladimiry]

We support down to eslint 2, and need to support the same node versions that a supported version of eslint does

Got it. So v2.20.1 => v6.x eslint-plugin-import bump is not considered.

Unfortunately I would not be interested in implementing glob support in no-restricted-paths using minimatch module having known that there are better options (minimatch by the way doesn’t declare engines.node prop but it runs node 4,6,7 only on Travis). So closing the issue again, this time with won't fix status.