Package Exports
- fluidify
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (fluidify) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Flulidify
Flulidify is a way to easily make fluent interfaces in coffeescript where the methods can be called in any order.
Installation
Via npm: place flulidify in the dependencies your package.json or run:
npm install flulidifyAlternatively grab dist/flulidify.js. There are no dependencies. Supports both browser (flulidify global) or node
(flulidify = require('flulidify')).
Examples
Say you wanted a fluent interface that looks like this:
modify(justCats)
.inStream(animalStream)
.using(meow)You also don't care which order the methods are called:
modify(justCats)
.using(meow)
.inStream(animalStream)You can make this work in coffeescript:
actualFunction = (predicate, stream, func) ->
# Your code here
modify = (predicate) ->
using: (func) ->
inStream: (stream) ->
actualFunction(predicate, stream, func)
inStream: (stream) ->
using: (func) ->
actualFunction(predicate, stream, func)However, this gets tedious, especially with more methods. With Flulidify it's easy:
modify = flulidify 'inStream', 'using', (predicate, {inStream: [stream], using: [func]}) ->
# Your code hereMore in depth, made up example:
foo(1, 2, 3)
.bar('a', 'b', 'c')
.baz('x', 'y', 'z')Would be created using:
foo = flulidify 'bar', 'baz', (one, two, three, {
bar: [ayy, bee, cee]
baz: [ex, why, zee]}) ->
# Your code hereFlulidify takes a number of method names and a callback. When all the methods have been called, the callback is executed with the initial arguments being the arguments of the first call, followed by a hash mapping method names to arguments they were called with. We use coffeescript's nifty destructuring syntax to achieve this.
Immutability
You can share partially applied fluent apis safely. Lets use this (contrived) builder example:
class Employee
constructor: (@name, @age, @salary) ->
employeeBuilder = flulidify 'name', 'email', 'age', ({
name: [name]
age: [age]
salary: [salary]}) ->
return new Customer(name, age, salary)We can now create a template employee with a fixed salary that we can assign names and ages to:
tenXDev = employeeBuilder().salary(200000)
dave = tenXDev.name('dave').age(27)
john = tenXDev.age(29).name('john')Hacking
Look inside the Gulpfile for the various tasks. To get started with autocompilation-and-tests-on-save run:
npm install --save-dev
./gulp watchCredits
Joe Lea for the original coffeescript fluent interface concept and bouncing off ideas for automating the pattern.