We had a case where the source glob could be different depending on build config (for example src/frontend/*/*/css/*.scss vs. src/frontend/namespace/themename/css/*.scss), but the destination directory is always the same skin. Without the base option those different globs would result in files being written in different directories, but setting the base option in gulp.src as src fixed this. However it wasn't yet possible here in gulp-watch-sass.
Setting the base path is possible in gulp-watch, so I thought it would make sense to also allow it here. I'm not sure about the usefulness of the other options in gulp-watch, but @sp00m can probably say if the whole options object could be passed into gulp-watch.
Coverage remained the same at 92.632% when pulling eca6489380c11a2f9c7643b4b2faa74daf5dc7c8 on aapokiiso:allow-base-option into b76eb820d9be78ac66df747dbbc8670ac00b1555 on sp00m:master.
We had a case where the source glob could be different depending on build config (for example
src/frontend/*/*/css/*.scss
vs.src/frontend/namespace/themename/css/*.scss
), but the destination directory is always the sameskin
. Without the base option those different globs would result in files being written in different directories, but setting the base option ingulp.src
assrc
fixed this. However it wasn't yet possible here ingulp-watch-sass
.Setting the base path is possible in
gulp-watch
, so I thought it would make sense to also allow it here. I'm not sure about the usefulness of the other options ingulp-watch
, but @sp00m can probably say if the wholeoptions
object could be passed intogulp-watch
.