arbaeen-web-app/node_modules/eslint-plugin-import/docs/rules/no-relative-parent-imports.md

# import/no-relative-parent-imports

Use this rule to prevent imports to folders in relative parent paths.

This rule is useful for enforcing tree-like folder structures instead of complex graph-like folder structures. While this restriction might be a departure from Node's default resolution style, it can lead large, complex codebases to be easier to maintain. If you've ever had debates over "where to put files" this rule is for you.

To fix violations of this rule there are three general strategies. Given this example:

```
numbers
└── three.js
add.js
```

```js
// ./add.js
export default function (numbers) {
  return numbers.reduce((sum, n) => sum + n, 0);
}

// ./numbers/three.js
import add from '../add'; // violates import/no-relative-parent-imports

export default function three() {
  return add([1, 2]);
}
```

You can,

1. Move the file to be in a sibling folder (or higher) of the dependency.

`three.js` could be be in the same folder as `add.js`:

```
three.js
add.js
```

or since `add` doesn't have any imports, it could be in it's own directory (namespace):

```
math
└── add.js
three.js
```

2. Pass the dependency as an argument at runtime (dependency injection)

```js
// three.js
export default function three(add) {
  return add([1, 2]);
}

// somewhere else when you use `three.js`:
import add from './add';
import three from './numbers/three';
console.log(three(add));
```

3. Make the dependency a package so it's globally available to all files in your project:

```js
import add from 'add'; // from https://www.npmjs.com/package/add
export default function three() {
  return add([1,2]);
}
```

These are (respectively) static, dynamic & global solutions to graph-like dependency resolution.

### Examples

Given the following folder structure:

```
my-project
├── lib
│   ├── a.js
│   └── b.js
└── main.js
```

And the .eslintrc file:
```
{
  ...
  "rules": {
    "import/no-relative-parent-imports": "error"
  }
}
```

The following patterns are considered problems:

```js
/**
 *  in my-project/lib/a.js
 */

import bar from '../main'; // Import parent file using a relative path
```

The following patterns are NOT considered problems:

```js
/**
 *  in my-project/main.js
 */

import foo from 'foo'; // Import package using module path
import a from './lib/a'; // Import child file using relative path

/**
 *  in my-project/lib/a.js
 */

import b from './b'; // Import sibling file using relative path
```