-
Notifications
You must be signed in to change notification settings - Fork 255
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
Refactoring getOptions #23
Conversation
Yep that's fine (theoretically). I suspect that the way you did the export won't get you the result that you're looking for though (You're not actually exporting getBaseOptions()). If you add a simple test that uses getBaseOptions() directly, you'll see what I mean (we should probably have a test on that anyway, since this is a coverage tool.). |
Also updated index.js to prevent any breaking API changes and added tests around both getOptions and getBaseOptions.
Good call on the exports, I totally added that as an after thought. I refactored the tests so the same tests will hit both |
Ha very nice... I'm re-running that one build and expect it to pass. Sometimes coveralls.io gets flakey when I hit it with multiple coverage reports at once. One question though: Don't you want index.js to export getBaseOptions? |
If you would like, I can add getBaseOptions to index.js. I was planning on just doing something like this var getBaseOptions = require('../lib/getOptions').getBaseOptions; Adding it to |
Thanks. Do you know when you are going to publish a new version of |
Just did! It's 2.3.0. Great work! Thanks for the help. Let me know if you need anything else. |
@cainus did you publish to npm? The latest version that I see out there is 2.2.0. |
Bah sorry... guess I skipped that step... just did it though. |
Here is an example of something that I think would work for the
grunt-karma-coveralls
plugin for issue #22.