there's following value in /home/user/project/.csscomb.json:
"exclude": [
"node_modules/**"
]
css files are passed to csscomb from find /home/user/project -name '*.css' command, which returns absolute paths
As a result all css files from node_modules are checked despite of exlude option
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1519037-exclude-paths-are-ignored-when-passing-absolute-paths-to-csscomb?utm_campaign=plugin&utm_content=tracker%2F214563&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F214563&utm_medium=issues&utm_source=github).
It is minimatch-specific behaviour, it can be "fixed" (with some caveats) by writing "**/node_modules/**", but it would be nice if csscomb could try to cut off pwd from the beginning of the absolute path.
/home/user/project
/home/user/project/.csscomb.json
:find /home/user/project -name '*.css'
command, which returns absolute pathsAs a result all css files from
node_modules
are checked despite ofexlude
option