-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Excluding files with custom loader not working #65
Comments
Excludes don't use globs, just prefix matching. You're certainly not the first to ask for this, though. I can probably hack up a fix, but not 'till later in the week. If you're really interested, I'd welcome a PR, although ideally one that's backwards compatible. |
If you've just got one file you want to exclude, then |
@jwalton thanks for the response. I am doing I read through the exclude code last night and wasn't really sure how it actually determines the file path from the |
The magic happens here, where we call into |
Interesting - so they are being excluded when I use |
Excludes now us globs! I'll close this, but feel free to raise another issue if you're still having problems. |
My
coffee-coverage-loader.coffee
looks like this:and I've tried all manner of globs for the exclude paths. For this library I've just got one file I want to instrument, and a
-cli.coffee
that I would like to ignore. Mymocha.opts
looks like this:The problem could be because of istanbul ignoring the
basePath
, but I'm not sure.I'm using the given
npm test
command from the Travis CI tutorial.I also tried using an
.istanbul.yml
file with no luck, mostly because I wasn't sure which options applied to instrumenting coffeescript...The text was updated successfully, but these errors were encountered: