Stream trigger and Inject opinions

[Will Squire]

Hey guys and girls,

Just finished (although, finished might not be the best word to use) creating two new Dart packages called Stream Trigger and Inject Module, and would love your feedback on them, good or bad :) . They were primarily developed for back-end web development, however they (Stream Trigger especially) would be applicable as general programming tools. 

To give a bit of a summary on each one:

Stream Trigger is more of a tool, it's used for streams and invokes functions based on the data going through streams. You define the 'trigger' data, and once that data is detected on a stream, it invokes the handler function for that trigger. This currently supports List<int>, need to make a few tweaks to broaden this out a bit. Returning data in the handler function will replace the trigger on the stream. By doing this, it is also capable of merging data streams (injecting one at a point into another) by returning a stream in the handler, replacing the trigger data with the stream data. See it here: https://pub.dartlang.org/packages/stream_trigger

Inject Module is much like the many templating engines you see, however it is built using streams, has a variable/definable syntax and really aims for 'logic-less' data files while the logic is done elsewhere from the file being read (unlike some that claim logic-less...). It is built on-top of Stream Trigger and can inject not just strings, but also other streams into a stream. Inject modules are 'stackable', Inject one inject module into another and receive a merged stream with the data starting and ending where expected. See it here: https://pub.dartlang.org/packages/inject_module

These are very brief overviews (and might not be the best way of explaining them), but let me know how I could make improvements in any way. 

Thank you for reading.

Will