-
-
Notifications
You must be signed in to change notification settings - Fork 70
Refactor/lint dirty modules only #59
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
Conversation
as opposed to reduce. also use lodash.defaultto for comparing numeric values to avoid falsy JS bugs
and clean up some assertions and specs
|
looks good to me 👍 |
|
Are there any other test cases you can think of? |
|
actually, can't think of anything else. all cases that I'm aware of are covered |
to enable the recursive flag in mocha.
|
@JaKXz, all works fine on my local with and without lintDirtyModulesOnly flag. The unrelated thing, I'm seeing that messages are duplicated when |
Verify that existing behaviour works as expected
1 similar comment
|
@sergesemashko would you mind making a new issue for that? I think I have a fix, I'll make a PR in the next few minutes. |
* refactor: use filter on filetimestamps' keys as opposed to reduce. also use lodash.defaultto for comparing numeric values to avoid falsy JS bugs * refactor: use Arrange Act Assert model for tests and clean up some assertions and specs * refactor: pulls out defaultFilesGlob constant * refactor: clean up typos * refactor: use .test.js file suffix to enable the recursive flag in mocha. * refactor: better names for all fixtures * tests: add coverage for without plugin config * tests: update NoErrorsPlugin tests Verify that existing behaviour works as expected * refactor: minor test tweaks * tests: correct test of empty plugin config * tests: remove extra context from lint dirty modules plugin
@sergesemashko to get a better handle on the code from #53 I took a stab at [some minor nits &] refactoring and staying green :) let me know if there's anything that concerns you.
Thanks!