Gulp-esque streams and operation piping.

[RichiCoder1]

See: https://github.com/gulpjs/gulp/blob/master/docs/API.md#gulpsrcglobs-options.
This:

gulp.src('client/templates/*.jade')
  .pipe(jade())
  .pipe(minify())
  .pipe(gulp.dest('build/minified_templates'));

Task("A")
  .Does(() =>
{
    Source("client/templates/*.jade")
        .Pipe(Jade)
        .Pipe(Minify)
        .Destination('build/minified_templates');
});

With this new Alias:

public static ICakePipe Source(this ICakeEnviroment enviroment, string globOrDirectoryName); 

Still chewing on how ICakePipe would function, how files are passed to stream Aliases, and other such things. Would follow the general idea that the functions would either be called for each file in the globbed file collection, or would return a func that accepts a file stream. The latter would change .Pipe(Jade) to .Pipe(Jade()), and would allow options to be passed to aliases.

Comments, opinions, etc?

[patriksvensson]

I'm not familiar with Gulp but will read the link you provided and digest it 😄

[RichiCoder1]

It's a very popular, if not defacto, build system in the JavaScript community. Has a lot of neat ideas.

[patriksvensson]

I think it looks neat 😄

Something like this could be used as a generic file/stream transformation mechanism in Cake.
It would probably be wise (as a first step) to implement it as an addin.

[RichiCoder1]

Absolutely. I don't think there's anything here that requires cake level support.
I may make that a personal project for funsies (on top of all my other languishing personal projects xD).

[RichiCoder1]

Here's an example implementation:
https://github.com/RichiCoder1/Cake.Streaming

It's still a rough work-in-progress. Would love opinions or feedback>
(Also, build.ps1 won't work just this sec, as I couldn't fix my .gitignore before my computer died and, as a result, some .cake utility files and the nuspec aren't commited. The solution should build fine)

Edit: Like on idea would be to add a Func<IReadOnlyList<PipeFile>, IReadOnlyList<PipeFile>> Pipe overload, for files that might want to process all files at once.
And to expose the underlying filepath directly for addins that might be interested in the file extension.
Edit: Edit: Also make the ToX() extensions work directly against Stream so this works:

var memoryStream = new MemoryStream();
var writer = new StreamWriter(memoryStream, new UTF8Encoding(true, false), 1024, false);
// becomes
var writer = memoryStream.ToWriter();

Edit: Edit: Edit: Also Destination converts piped files to a flat structure. It really should preserve source structure unless told to flatten. Ok, now I think I'm done with these edits...

[khellang]

You could also take a look at PVC if you want some inspiration for a streaming build-system in C# 😉