PromisePipe
PromisePipe copied to clipboard
edjafarov
PromisePipe - reusable cross process promise chains
GitHub changed the way Markdown headings are parsed, so this change fixes it. See [bryant1410/readmesfix](https://github.com/bryant1410/readmesfix) for more information. Tackles bryant1410/readmesfix#1
Right now on unhandled exception it just fails like this: ``` Failed inside test ReferenceError: ff is not defined Object.test@/Users/edjafarov/work/PromisePipe/tests/PromisePipe.error.spec.js:28:16 newArgFunc@/Users/edjafarov/work/PromisePipe/src/PromisePipe.js:456:26 {anonymous}() ($)$$internal$$tryCatch@/Users/edjafarov/work/PromisePipe/node_modules/es6-promise/dist/es6-promise.js:304:16 {anonymous}() ($)$$internal$$invokeCallback@/Users/edjafarov/work/PromisePipe/node_modules/es6-promise/dist/es6-promise.js:316:17 {anonymous}()@/Users/edjafarov/work/PromisePipe/node_modules/es6-promise/dist/es6-promise.js:874:13 {anonymous}() ($)$asap$$flush@/Users/edjafarov/work/PromisePipe/node_modules/es6-promise/dist/es6-promise.js:111:9 [email protected]:442:13 ```...
if there is client-server, server-worker1, server-worker2 than if pipe need to get worker1-worker2, it should resolve back to worker1-server and then go into server-worker2 upd: Workers probably do not know...
Make router based on the prototype https://github.com/edjafarov/PromisePipe/tree/master/example/PPRouter
The Pipe is controlling what chains should be executed where. That gives ability for pipe to distribute the load in a smart/dummy way. For example it could use a simple...
Maybe it might make sense to use existing cpecified protocol http://www.jsonrpc.org/specification
This should be analysed. The pipe itself is pretty simple. The PromisePipe can record actions and auto generate tests code.
Kind of red button in the right bottom corner that would record all business logic. And the log could be copypasted by Tester into the ticket. And player for developer...