Open bali182 opened 8 years ago
To my knowledge, there isn't a way to exclude files from being blacklisted once they have been. This would probably be a good enhancement though.
You can always put a note in the README
for your provider to suggest that people alter the blacklist. Or even do something like on startup of your provider, it checks the blacklist and pops up a dialog asking permission to change the blacklist on behalf of the user.
Hmm, mentioning this in the readme seems like a good workaround, thanks.
TL;DR
Is there a way to remove some
.foo
kind of (hidden?) files from the blacklist (e.g.:.babelrc
in my case)?Long version:
I'm creating an autocomplete provider for
.json
files for known and commonly used schemas, one of these is.babelrc
. Since the default blacklist configuration is.*
, it matches withminimatch
to.anything
, so my provider has no chance to kick in. Is there a way to disable this behaviour for my provider?