max-depth would ensure that the maximum directory depth is not more than X. For instances, if we have the following project structure
- /
- index.js
- lib
- utils
- foo.js
Thus foo.js is located at depth is 3 and the rule will fail if max-depth is set to 2.
Not sure if this is something we actually want. But the higher the depth, the more complex the project structure becomes. So it might be useful. And if so, wat would we use as value and should it be an error or a warning?
max-depth
would ensure that the maximum directory depth is not more than X. For instances, if we have the following project structureThus
foo.js
is located at depth is3
and the rule will fail ifmax-depth
is set to2
.Not sure if this is something we actually want. But the higher the depth, the more complex the project structure becomes. So it might be useful. And if so, wat would we use as value and should it be an error or a warning?
// @sindresorhus @jamestalmage @kevva @jfmengels