Add 'allow' option to the no-relative-parent-imports rule or 'ignoreChildren' option to no-internal-modules rule.

[nikopavlica]

Our use case is to have some util classes/functions in a folder on top and then always import using relative path.
Eg.

src/
 utils/
   util1.js
 comp1/
   index.js
 comp2/
   index.js

From src/comp1/index.js i'd like to be able to import from ../utils/util1 but prohibit import from ../comp2

To achieve this, I see two options:

1. add 'allow' option to no-relative-parent-imports rule (in the same form as no-internal-modules 'allow'), eg.

"import/no-relative-parent-imports": [ "error", { "allow": ["**/src/utils/**"] } ]

2. add 'ignoreChildren' option to no-internal-modules to only inspect parent's internal modules, eg.

"import/no-internal-modules": [ "error", { "allow": ["**/src/utils/**"], "ignoreChildren": true  } ]

I'm willing to provide a PR to any of the rules.

[ljharb]

The former seems reasonable to me.

Any progress on this yet ?

I've been looking for exactly this (option 1).

[neolivz]

There is already an option to do this with ignore regex
"import/no-relative-parent-imports": [ "error", { ignore: [".*/shared/.*"], }, ],

[tmtron]

There is already an option to do this with ignore regex "import/no-relative-parent-imports": [ "error", { ignore: [".*/shared/.*"], }, ],

Thanks for that comment. I didn't know that ignore can also be used per rule. When reading the docs, I saw the ignore option, but thought that it can only be used on the plugin level: i.e. that it affects all import-rules.
I think this should be mentioned in the docs explicitly and also the no-relative-parent-imports should mention ignore as a 4th option to "fix" the validation.