Tried adapting for per-provider user-configurable file blacklisting that didn't require any chances in existing provider implementations, but cannot figure out a way to reliably look up the blacklist configuration key (if autocomplete-plus didn't automatically register a FuzzyProvider, this probably wouldn't be a problem, so the next revision should make this package merely a library with no user functionality).
Provider now provides simple mechanism for user-configurable per-provider file blacklisting. In order to do this, the automatic loading of a FuzzyProvider has been disabled.
*N.B.*: Now that a FuzzyProvider no longer automatically registers, most of the package tests fail.
Removed debugging comments.
Tweaked the package-name-checking functionality of Provider->currentFileBlacklisted for compatibility with the testing environment.
Removed checking the configuration value for autocomplete-plus.fileBlacklist, since we are no longer trying to maintain drop-in compatibility with the autocomplete-plus package.
Fixed an unmatched parenthesis.
Tweaked the file blacklist processing so that glob brace expansion works as expected. This means commas can no longer be used except for brace expansion.
Removed default configuration variables. Adjusted configuration variables in specs.
Moved file blacklist checking back to autocomplete-view.coffee, moved package name checking to autocomplete.coffee, and reworked the way default configuration values are handled.
Manually create and register FuzzyProviders in the specs that expect them.
Use {@package.name} in FuzzyProvider so that it's calling-package agnostic.
Wrote CHANGELOG and README, and updated package.json.