[Feature Request] Allow to configure maximum depth of relative imports

[Dema]

I use some kind of fractal design pattern plus atomic design for my apps and usually it is pretty normal to have imports one or two folders up like '../MyComponent' or ../../MyComponent.

Because these are "related" components I'm okay with them being imported relatively, but I want to disable imports with 3 or more "../" path segments. It would be great to add some config parameter like maxDepth:2 for these cases.

[jochemvogel]

Totally agree. Sometime it just doesn't make sense to only accept absolute paths. Nonetheless, a maxDepth of more than two is unnecessary.

Imagine having the following folder structure:

src
├── utils
│   ├── isPhoneNumber
│   └──── __tests__
│   └────── index.test.ts
│   └──── index.ts

It just doesn't make any sense to use import isPhoneNumber from src/utils/isPhoneNumber/index in your test file (in our opinion).

In this case we prefer using import isPhoneNumber from '../index';

---

Tried to implement it by myself, but it's too complex for me.

First I added the maxDepth property to line 40.

Then I tried to update the getAbsolutePath() function with a maxDepth condition.
(Long story short: if maxDepth is set to one --> add '../' etc. etc.)

At this point it got to complex for me. Somehow you need to prefix ../ or ../../ based on the maxDepth that is configured. But don't just add it, because adding it to the absolute path won't work. This obviously will create something like ../../src/utils/isPhoneNumber/index. That's something you don't want.

---

Is someone capable enough to implement this or is this too complex? Currently I'm unable to use it, because of the reasons I gave above. 🙂

Edit: There are too many places, so fixing it with a eslint disable is in our opinion worse than we have right now.