-
Notifications
You must be signed in to change notification settings - Fork 116
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
data.files is replaced #236
Comments
@bkrrrr I investigated the issue and I understand the code now. However, just as you, I also thought it was a mistake. The code looks like it is forgetting to add the contents of The |
- This feature was added in pull #150 without a test. It now has a test. - The code was applying the flatten operation to all input, but should really only be applied to `options.files`, not to this.files from Grunt, which is already processed. - The code was checking `data.files` but using `this.files`. This is working correctly, but looks confusing to a reader. `data.files` is the raw input, and `this.files` is the version of that input after processing by Grunt. To improve readability, use that same reference for the check as well. In order to keep behaviour identical, use the array's length property to determine whether it was set. The files array is always available from Grunt, and can be safely accessed without additional check. This is covered by the karma:config test case, which specifies neither options.files nor data.files. Ref #150. Closes #236.
- This feature was added in pull #150 without a test. It now has a test. - The code was applying the flatten operation to all input, but should really only be applied to `options.files`, not to this.files from Grunt, which is already processed. - The code was checking `data.files` but using `this.files`. This is working correctly, but looks confusing to a reader. `data.files` is the raw input, and `this.files` is the version of that input after processing by Grunt. To improve readability, use that same reference for the check as well. In order to keep behaviour identical, use the array's length property to determine whether it was set. The files array is always available from Grunt, and can be safely accessed without additional check. This is covered by the karma:config test case, which specifies neither options.files nor data.files. Ref #150. Closes #236.
- This feature was added in pull #150 without a test. It now has a test. - The code was applying the flatten operation to all input, but should really only be applied to `options.files`, not to this.files from Grunt, which is already processed. - The code was checking `data.files` but using `this.files`. This is working correctly, but looks confusing to a reader. `data.files` is the raw input, and `this.files` is the version of that input after processing by Grunt. To improve readability, use that same reference for the check as well. In order to keep behaviour identical, use the array's length property to determine whether it was set. The files array is always available from Grunt, and can be safely accessed without additional check. This is covered by the karma:config test case, which specifies neither options.files nor data.files. Ref #150. Closes #236.
It seems like its not possible right now to use files in options and another target. Or at least the output is not as expected.
What is the idea behind that block (grunt-karma.js:74)?
by replacing this with:
files is usable as expected
The text was updated successfully, but these errors were encountered: