Closed chris54721 closed 7 years ago
You need to rebase on master since I just landed #64.
@generalov Any thoughts on this?
Well that was bad timing.
Very interesting, guys! In the ideal, any promise rejects should be handled. Could you please add some unit tests for more details to describe this case?
I've nether come across this issue in our project. It seems the issue is avoided by the gulp-if
in the pipe: .pipe($.if('**/*.css', cssChannel(), $.gulp.dest(destPath)))
So just files are passed to the cssChannel
substream where the gulp-changed actually is used.
That's the expected behavior for the directories?
The 1 and 2 could be solved by the appropriate error handling in the ".catch" function. The 3 by updating the documentation with may be a gulp-if example. The 4 is required the investigation.
I think the best solution would be pushing directories to the stream only if there are some file changes in them, since it's probably the behavior most users would expect IMO, and we don't need to add a dependency on gulp-if when using glob patterns.
I think the best solution would be pushing directories to the stream only if there are some file changes in them
I think that makes the most sense too.
@chris54721 Are you interested in updating your PR?
At the moment unfortunately I'm a bit busy IRL, I should be able to work on it in a couple of weeks.
Alright. I'm closing this for now. But ping me here when you're ready and I'll reopen ;)
Workaround using gulp-if:
[...].pipe(gulpIf(f => !f.isDirectory(), gulpChanged([...])))
compareSha1Digest
does not check whethersourceFile
represents a directory, which can happen for example when using glob patterns forsrc
. This PR makes sure only files are processed; at the moment if the source paths contain a directory the following error is thrown: