About project structure about stylelint

[MoOx]

__tests__ is a common pattern used by big projects like react. It avoid to get a huge test folder with duplicated tree structure and ensure modularity of the components. Like having multiples .md files near the corresponding code.

For the index.js we might be able to get rid of it using some others tricks that this kind of exports.
I will think about it.

[tunnckoCore]

duplicated tree structure and ensure modularity of the components

omg. now tree structure is duplicated and confusing, lol
its enough to have just one test/ folder and in her to have fixtures/ or something..

[MoOx]

src/rules/*.js
test/rules/*.js
docs/rules/*.js

vs

src/rules/*/*.js
src/rules/*/*.md
src/rules/*/__tests__/*.js

To write decoupled code it make more sense to me.

omg. now tree structure is duplicated and confusing, lol

I work with a lot of people in different teams that like this way that encourage modularity.

Sometimes __tests__ is test but it doesn't change the way files are arranged.
The most I work with fixtures, the more I like to write tiny decoupled components that have fixtures embed in the tests. Like here stylelint already does and eslint does too.
An good example of painful fixtures to maintain is my cssnext project (btw I will change that soon).
es6 template string (multilines string) might help too to have embed fixtures.

[davidtheclark]

I also think that having tests right there next to the thing they're testing makes sense for this project, which will end up having so many relatively independent little parts.