This is frustrating me as well.
In my example, node_modules
is a directory I want to exclude globally, except when I’m working on one certain project that uses that as part of its naming elsewhere.
Interestingly not only does it not work at the folders
level of a project, it also doesn’t work in the settings
override portion.
So in a project you can do:
"settings": {
"caret": "solid"
}
For example, which will change the caret for just that project. However, the "folder_exclude_pattern"
parameter seems to get ignored.
I realise it’s hard to manage include and exclude features, because of the inherent complexity in working out the ordering, but I think if project settings were able to override this (or extend it) that might give enough flexibility?
One possible ordering could be (most important rule first)
- folder exclude
- folder include
- project settings exclude
- project settings include
- global settings exclude
- global settings include
- defaults