fluents / chain-able Goto Github PK

• put all internal methods onto a single property, for better:

• access/crud/structure
• minifying/perf
• debugging/testing

# compose

Ⓢ

• neutrinojs/webpack-chain#28
• https://github.com/facebook/immutable-js/blob/master/src/OrderedMap.js
• 344bb6b#diff-7fb9367b7a114b367ef79fb59738bccbR158

• so they can be optimized easier externally when used as functions
• so it can provide a fluent interface for the iterating, reducing the different iterators required for different apis
• so it can add compatible api methods for mappers when using with existing libs such as ramda & lodash

so get(obj, path) can check isMap

from https://github.com/eliperelman

• decision tree
• easy inlining with no unexpected types

• results

instead of spread out functions that clutter each chainable instance, now that the foundation is well-tested & well-used, a better approach would be use the "chainable` approach to create methods

related:
#7

• output the string code for the methods created in method chain

https://github.com/joinspontaneous/frisbee

methodchain

• memoize
• better transforms
• change compose which has the classes as properties not flat exports in index
• es6 export file
• tests for decorators in compose
• split methodchain into core, and then almost all method-builders could be added as plugin types
• pool method-builder rather than try & force garbage collection