Add ability to pipe SassDoc into stdin - #315
Conversation
|
Awesome! I would rather remove the |
|
Like @valeriangalliat said. We can assume that the omission of |
|
Okay for removing No Gulp pipeline: |
|
It's interesting, but I really don't believe it's a "normal" use case. It makes no sense to me to both documentize and compile SCSS in the same pipeline, and it gives the impression that SassDoc is filtering the stream, which is not the case. Additionnally it don't allows parallel running, while defining this with, for example, two distinct makefile tasks could be parallelized. |
|
If I'm not mistaken, it's similar to: var gulp = require('gulp');
var sass = require('gulp-sass');
var sassdoc = require('sassdoc');
gulp.task('styles', function () {
return gulp.src('./file.scss')
.pipe(sassdoc({ verbose: true }))
.pipe(sass());
});It should also be able to: |
|
Yep. I don't use Gulp so I don't know if it makes sense, but for sure it looks odd in a shell pipeline. |
|
Not 100% sure it makes sense, but that was one of the goal to the whole stream refactor, being able to pipe SassDoc in a Gulp pipeline, without requiring a dedicated task. That's why we pass trough the files also. |
|
@pascalduez and @valeriangalliat you are both right. In the context of gulp this is perfect but behaviour like this isn't expected on the shell pipe. Nevertheless it is not that bad to have it. |
|
Okay guys, no stdout !! |
|
Right, all good there then? |
Add ability to pipe SassDoc into `stdin`
Introduce a new
-s --stdinflag to make it clear/intentional ?Example:
cat test/data/test.scss | bin/sassdoc -vs