{"_id":"noflo-lift","_rev":"45-41b1743c0a6d0c3caa8888056c3ac22a","name":"noflo-lift","description":"Lift Packets for Processing in NoFlo","dist-tags":{"latest":"0.0.12"},"versions":{"0.0.1":{"name":"noflo-lift","description":"Lift Packets for Processing in NoFlo","keywords":["noflo","lift","extract","subset"],"author":{"name":"Kenneth Kan","email":"kenhkan@gmail.com"},"version":"0.0.1","licenses":[{"type":"MIT","url":"https://github.com/kenhkan/noflo-lift/blob/master/LICENSE.md"}],"engines":{"node":">=0.6.0"},"repository":{"type":"git","url":"git://github.com/kenhkan/noflo-lift"},"dependencies":{"noflo":"0.3.x","underscore":"1.4.x","underscore.string":"2.3.x","node-uuid":"1.4.x","noflo-flow":"0.0.x","noflo-groups":"0.0.x","noflo-packets":"0.0.x"},"devDependencies":{"coffeelint":"*","coffee-script":"1.6.x","noflo-test":"https://github.com/kenhkan/noflo-test/tarball/develop"},"noflo":{"components":{"Extractor":"./components/Extractor.coffee","Assembler":"./components/Assembler.coffee","RandomToken":"./components/RandomToken.coffee"},"graphs":{"Lift":"./graphs/Lift.fbp","Extract":"./graphs/Extract.fbp","Assemble":"./graphs/Assemble.fbp"}},"scripts":{"pretest":"./node_modules/.bin/coffeelint -r components","test":"./node_modules/.bin/noflo-test --spec test/*.coffee"},"readme":"Lift Packets for Processing in NoFlo [](https://travis-ci.org/kenhkan/noflo-lift)\n===============================\n\nIn a [NoFlo](http://noflojs.org/) program, how the program processes\ndata is more important than the data structure. It is evident in that\nmost NoFlo programs expect a rather flat data structure of a series of\npackets enclosed in one or two levels of groups.\n\nWhen your program expects a more complex data structure, it is useful to\nbe able to extract a subset of the structure, do some work, and plug it\nright back into where it was extracted from. noflo-lift allows you to\nliterally \"lift\" a subset of the data structure by providing a pattern\nobject for further processing on just that one piece. It then accepts\nsome data structure that noflo-lift would then insert back in place.\n\n\nIn Ports\n------------------------------\n\nnoflo-lift accepts data via these ports:\n\n#### IN\n\nAny valid NoFlo data structure\n\n#### PATTERN\n\nA pattern is a path-like array denoting the group structure to extract.\nFor instance, in XML schematics, if you have an incoming data structure:\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\nAnd you want to extract just `GroupC` for processing, you would pass in,\nin JSON:\n\n [ \"GroupA\", \"GroupB\", \"GroupC\" ]\n\n#### RETURN\n\nThe processed data structure must be returned to this port to continue\nits journal through the `OUT` port. See the `PROCESS` out port for\ndetails.\n\n#### CACHESIZE\n\nnoflo-lift does not have a cache limit as it expects you to finish\nprocessing on all opened requests. You may optionally set a cache size\nif you deal with asynchronous operations that may fail.\n\n\nOut Ports\n------------------------------\n\nnoflo-lift emits data via these ports:\n\n#### OUT\n\nThe data structure that has been processed and plugged back in is\nemitted to this port.\n\n#### PROCESS\n\nThe *extracted* data structure is emitted here. It is grouped at the\ntop-level by a token, which must group the processed data structure on\nreturn to the `RETURN` in port.\n","readmeFilename":"README.md","_id":"noflo-lift@0.0.1","dist":{"shasum":"0e90ae99b83ad17daae818d1091bdc22b39dbff6","tarball":"https://registry.npmjs.org/noflo-lift/-/noflo-lift-0.0.1.tgz","integrity":"sha512-mblEafl3Wpv2bhON1QtBUG7WEjov5lYie37YplbyCEXO2IQHkBVeg6Tbk65Fe9LCDOEK/XnpIGyxtnnccvh5QQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCNKW1fJjaaYbQZCM9s7u9zcR+ziy3HI+eldLihfqd9IQIhAM8sVU9ViElaRKioyqqxwnUnkD/vAMY+Bz5Tu8B73Svh"}]},"_from":".","_npmVersion":"1.2.18","_npmUser":{"name":"kenhkan","email":"kenhkan@gmail.com"},"maintainers":[{"name":"kenhkan","email":"kenhkan@gmail.com"}],"directories":{}},"0.0.3":{"name":"noflo-lift","description":"Lift Packets for Processing in NoFlo","keywords":["noflo","lift","extract","subset"],"author":{"name":"Kenneth Kan","email":"kenhkan@gmail.com"},"version":"0.0.3","licenses":[{"type":"MIT","url":"https://github.com/kenhkan/noflo-lift/blob/master/LICENSE.md"}],"engines":{"node":">=0.6.0"},"repository":{"type":"git","url":"git://github.com/kenhkan/noflo-lift"},"dependencies":{"noflo":"0.3.x","underscore":"1.4.x","underscore.string":"2.3.x","noflo-swiss":"0.0.x","noflo-flow":"0.0.x","noflo-groups":"0.0.x","noflo-packets":"0.0.x"},"devDependencies":{"coffeelint":"*","coffee-script":"1.6.x","noflo-test":"https://github.com/kenhkan/noflo-test/tarball/master"},"noflo":{"components":{"Extractor":"./components/Extractor.coffee","Assembler":"./components/Assembler.coffee"},"graphs":{"Lift":"./graphs/Lift.fbp","Extract":"./graphs/Extract.fbp","Assemble":"./graphs/Assemble.fbp"}},"scripts":{"pretest":"./node_modules/.bin/coffeelint -r components","test":"./node_modules/.bin/noflo-test --spec test/*.coffee"},"readme":"Lift Packets for Processing in NoFlo [](https://travis-ci.org/kenhkan/noflo-lift)\n===============================\n\nIn a [NoFlo](http://noflojs.org/) program, how the program processes\ndata is more important than the data structure. It is evident in that\nmost NoFlo programs expect a rather flat data structure of a series of\npackets enclosed in one or two levels of groups.\n\nWhen your program expects a more complex data structure, it is useful to\nbe able to extract a subset of the structure, do some work, and plug it\nright back into where it was extracted from. noflo-lift allows you to\nliterally \"lift\" a subset of the data structure by providing a pattern\nobject for further processing on just that one piece. It then accepts\nsome data structure that noflo-lift would then insert back in place.\n\n\nIn Ports\n------------------------------\n\nnoflo-lift accepts data via these ports:\n\n#### IN\n\nAny valid NoFlo data structure\n\n#### PATTERN\n\nA pattern is a path-like array denoting the group structure to extract.\nFor instance, in XML schematics, if you have an incoming data structure:\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\nAnd you want to extract just `GroupC` for processing, you would pass in,\nin JSON:\n\n [ \"GroupA\", \"GroupB\", \"GroupC\" ]\n\n#### RETURN\n\nThe processed data structure must be returned to this port to continue\nits journal through the `OUT` port. See the `PROCESS` out port for\ndetails.\n\n#### CACHESIZE\n\nnoflo-lift does not have a cache limit as it expects you to finish\nprocessing on all opened requests. You may optionally set a cache size\nif you deal with asynchronous operations that may fail.\n\n\nOut Ports\n------------------------------\n\nnoflo-lift emits data via these ports:\n\n#### OUT\n\nThe data structure that has been processed and plugged back in is\nemitted to this port.\n\n#### PROCESS\n\nThe *extracted* data structure is emitted here. It is grouped at the\ntop-level by a token, which must group the processed data structure on\nreturn to the `RETURN` in port.\n","readmeFilename":"README.md","_id":"noflo-lift@0.0.3","dist":{"shasum":"3268c49acea94a9756aab64c0affc0fd223c78ba","tarball":"https://registry.npmjs.org/noflo-lift/-/noflo-lift-0.0.3.tgz","integrity":"sha512-6QYKgVnyMyKbKbdL3nI0Fn0CSaSqGYbAnLrPUjVyjYI7q54hYdq/onIlDRdaBolVJHIpn/cfiFb04YY1jcP5QQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCB7zKez2kvN6MWl25C9nGxMMZoB5AukEOum4aSwq2FEgIgDUb6DbKDuNmA+3lG7p+G4DxXcogzGG0jG6OJVZDnORE="}]},"_from":".","_npmVersion":"1.2.18","_npmUser":{"name":"kenhkan","email":"kenhkan@gmail.com"},"maintainers":[{"name":"kenhkan","email":"kenhkan@gmail.com"}],"directories":{}},"0.0.4":{"name":"noflo-lift","description":"Lift Packets for Processing in NoFlo","keywords":["noflo","lift","extract","subset"],"author":{"name":"Kenneth Kan","email":"kenhkan@gmail.com"},"version":"0.0.4","licenses":[{"type":"MIT","url":"https://github.com/kenhkan/noflo-lift/blob/master/LICENSE.md"}],"engines":{"node":">=0.6.0"},"repository":{"type":"git","url":"git://github.com/kenhkan/noflo-lift"},"dependencies":{"noflo":"0.3.x","underscore":"1.4.x","underscore.string":"2.3.x","noflo-swiss":"0.0.x","noflo-flow":"0.0.x","noflo-groups":"0.0.x","noflo-packets":"0.0.x"},"devDependencies":{"coffeelint":"*","coffee-script":"1.6.x","noflo-test":"https://github.com/kenhkan/noflo-test/tarball/master"},"noflo":{"components":{"Extractor":"./components/Extractor.coffee","Assembler":"./components/Assembler.coffee"},"graphs":{"Lift":"./graphs/Lift.fbp","Extract":"./graphs/Extract.fbp","Assemble":"./graphs/Assemble.fbp"}},"scripts":{"pretest":"./node_modules/.bin/coffeelint -r components","test":"./node_modules/.bin/noflo-test --spec test/*.coffee"},"readme":"Lift Packets for Processing in NoFlo [](https://travis-ci.org/kenhkan/noflo-lift)\n===============================\n\nIn a [NoFlo](http://noflojs.org/) program, how the program processes\ndata is more important than the data structure. It is evident in that\nmost NoFlo programs expect a rather flat data structure of a series of\npackets enclosed in one or two levels of groups.\n\nWhen your program expects a more complex data structure, it is useful to\nbe able to extract a subset of the structure, do some work, and plug it\nright back into where it was extracted from. noflo-lift allows you to\nliterally \"lift\" a subset of the data structure by providing a pattern\nobject for further processing on just that one piece. It then accepts\nsome data structure that noflo-lift would then insert back in place.\n\n\nIn Ports\n------------------------------\n\nnoflo-lift accepts data via these ports:\n\n#### IN\n\nAny valid NoFlo data structure\n\n#### PATTERN\n\nA pattern is a path-like array denoting the group structure to extract.\nFor instance, in XML schematics, if you have an incoming data structure:\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\nAnd you want to extract just `GroupC` for processing, you would pass in,\nin JSON:\n\n [ \"GroupA\", \"GroupB\", \"GroupC\" ]\n\n#### RETURN\n\nThe processed data structure must be returned to this port to continue\nits journal through the `OUT` port. See the `PROCESS` out port for\ndetails.\n\n#### CACHESIZE\n\nnoflo-lift does not have a cache limit as it expects you to finish\nprocessing on all opened requests. You may optionally set a cache size\nif you deal with asynchronous operations that may fail.\n\n\nOut Ports\n------------------------------\n\nnoflo-lift emits data via these ports:\n\n#### OUT\n\nThe data structure that has been processed and plugged back in is\nemitted to this port.\n\n#### PROCESS\n\nThe *extracted* data structure is emitted here. It is grouped at the\ntop-level by a token, which must group the processed data structure on\nreturn to the `RETURN` in port.\n","readmeFilename":"README.md","_id":"noflo-lift@0.0.4","dist":{"shasum":"015f824838c1b7f35604649cec6a0fa0701c5468","tarball":"https://registry.npmjs.org/noflo-lift/-/noflo-lift-0.0.4.tgz","integrity":"sha512-fk1UlFNrjSsnjQP+aRx+7tZdhC7ANChyt8juwYo5TwfYHNGEEfCyjDpjg39eUaRc0I3sNcYYJoYgtw/k6m0cLA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCID/BGlDNsRJF/fTKkqTcD77nkN78DDYqdoYyuVei8PnRAiBnfN24sn3TaRs3n8SbPvAnwZfBNfgAXPm2i2K1jEh/rg=="}]},"_from":".","_npmVersion":"1.2.18","_npmUser":{"name":"kenhkan","email":"kenhkan@gmail.com"},"maintainers":[{"name":"kenhkan","email":"kenhkan@gmail.com"}],"directories":{}},"0.0.5":{"name":"noflo-lift","description":"Lift Packets for Processing in NoFlo","keywords":["noflo","lift","extract","subset"],"author":{"name":"Kenneth Kan","email":"kenhkan@gmail.com"},"version":"0.0.5","licenses":[{"type":"MIT","url":"https://github.com/kenhkan/noflo-lift/blob/master/LICENSE.md"}],"engines":{"node":">=0.6.0"},"repository":{"type":"git","url":"git://github.com/kenhkan/noflo-lift"},"dependencies":{"noflo":"https://github.com/kenhkan/noflo/tarball/master","underscore":"1.4.x","underscore.string":"2.3.x","noflo-swiss":"0.0.x","noflo-flow":"0.0.x","noflo-groups":"0.0.x","noflo-packets":"0.0.x"},"devDependencies":{"coffeelint":"*","coffee-script":"1.6.x","noflo-test":"https://github.com/kenhkan/noflo-test/tarball/master"},"noflo":{"components":{"Extractor":"./components/Extractor.coffee","Assembler":"./components/Assembler.coffee"},"graphs":{"Lift":"./graphs/Lift.fbp","Extract":"./graphs/Extract.fbp","Assemble":"./graphs/Assemble.fbp"}},"scripts":{"pretest":"./node_modules/.bin/coffeelint -r components","test":"./node_modules/.bin/noflo-test --spec test/*.coffee"},"readme":"Lift Packets for Processing in NoFlo [](https://travis-ci.org/kenhkan/noflo-lift)\n===============================\n\nIn a [NoFlo](http://noflojs.org/) program, how the program processes\ndata is more important than the data structure. It is evident in that\nmost NoFlo programs expect a rather flat data structure of a series of\npackets enclosed in one or two levels of groups.\n\nWhen your program expects a more complex data structure, it is useful to\nbe able to extract a subset of the structure, do some work, and plug it\nright back into where it was extracted from. noflo-lift allows you to\nliterally \"lift\" a subset of the data structure by providing a pattern\nobject for further processing on just that one piece. It then accepts\nsome data structure that noflo-lift would then insert back in place.\n\n\nIn Ports\n------------------------------\n\nnoflo-lift accepts data via these ports:\n\n#### IN\n\nAny valid NoFlo data structure\n\n#### PATTERN\n\nA pattern is a path-like array denoting the group structure to extract.\nFor instance, in XML schematics, if you have an incoming data structure:\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\nAnd you want to extract just `GroupC` for processing, you would pass in,\nin JSON:\n\n [ \"GroupA\", \"GroupB\", \"GroupC\" ]\n\n#### RETURN\n\nThe processed data structure must be returned to this port to continue\nits journal through the `OUT` port. See the `PROCESS` out port for\ndetails.\n\n#### CACHESIZE\n\nnoflo-lift does not have a cache limit as it expects you to finish\nprocessing on all opened requests. You may optionally set a cache size\nif you deal with asynchronous operations that may fail.\n\n\nOut Ports\n------------------------------\n\nnoflo-lift emits data via these ports:\n\n#### OUT\n\nThe data structure that has been processed and plugged back in is\nemitted to this port.\n\n#### PROCESS\n\nThe *extracted* data structure is emitted here. It is grouped at the\ntop-level by a token, which must group the processed data structure on\nreturn to the `RETURN` in port.\n","readmeFilename":"README.md","_id":"noflo-lift@0.0.5","dist":{"shasum":"618f8d46bd1898d58d1eb164f57d84649d50ba3c","tarball":"https://registry.npmjs.org/noflo-lift/-/noflo-lift-0.0.5.tgz","integrity":"sha512-Vg/bKN3HZOhBW89GpEY1aJZNHNdu8HkFYhMBnIWfUC7gKYZeOckmh0SHLQucvwcZut7jf5EirZDI3J+Hix+ouQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIEBluwPTHKfGUGPU3nyS/Gr+LKLV75a6BIrTrNNhfY3FAiEA8fQE63UwtbOAL71B3+C3BoQTlr5xzlLvW2mtAXor7AE="}]},"_from":".","_npmVersion":"1.2.18","_npmUser":{"name":"kenhkan","email":"kenhkan@gmail.com"},"maintainers":[{"name":"kenhkan","email":"kenhkan@gmail.com"}],"directories":{}},"0.0.6":{"name":"noflo-lift","description":"Lift Packets for Processing in NoFlo","keywords":["noflo","lift","extract","subset"],"author":{"name":"Kenneth Kan","email":"kenhkan@gmail.com"},"version":"0.0.6","licenses":[{"type":"MIT","url":"https://github.com/kenhkan/noflo-lift/blob/master/LICENSE.md"}],"engines":{"node":">=0.6.0"},"repository":{"type":"git","url":"git://github.com/kenhkan/noflo-lift"},"dependencies":{"noflo":"https://github.com/kenhkan/noflo/tarball/master","underscore":"1.4.x","underscore.string":"2.3.x","noflo-swiss":"0.0.x","noflo-flow":"0.0.x","noflo-groups":"0.0.x","noflo-packets":"0.0.x"},"devDependencies":{"coffeelint":"*","coffee-script":"1.6.x","noflo-test":"https://github.com/kenhkan/noflo-test/tarball/master"},"noflo":{"components":{"Extractor":"./components/Extractor.coffee","Assembler":"./components/Assembler.coffee"},"graphs":{"Lift":"./graphs/Lift.fbp"}},"scripts":{"pretest":"./node_modules/.bin/coffeelint -r components","test":"./node_modules/.bin/noflo-test --spec test/*.coffee"},"readme":"Lift Packets for Processing in NoFlo [](https://travis-ci.org/kenhkan/noflo-lift)\n===============================\n\nIn a [NoFlo](http://noflojs.org/) program, how the program processes\ndata is more important than the data structure. It is evident in that\nmost NoFlo programs expect a rather flat data structure of a series of\npackets enclosed in one or two levels of groups.\n\nWhen your program expects a more complex data structure, it is useful to\nbe able to extract a subset of the structure, do some work, and plug it\nright back into where it was extracted from. noflo-lift allows you to\nliterally \"lift\" a subset of the data structure by providing a pattern\nobject for further processing on just that one piece. It then accepts\nsome data structure that noflo-lift would then insert back in place.\n\n\nIn Ports\n------------------------------\n\nnoflo-lift accepts data via these ports:\n\n#### IN\n\nAny valid NoFlo data structure\n\n#### PATTERN\n\nA pattern is a path-like array denoting the group structure to extract.\nFor instance, in XML schematics, if you have an incoming data structure:\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\nAnd you want to extract just `GroupC` for processing, you would pass in,\nin JSON:\n\n [ \"GroupA\", \"GroupB\", \"GroupC\" ]\n\n#### RETURN\n\nThe processed data structure must be returned to this port to continue\nits journal through the `OUT` port. See the `PROCESS` out port for\ndetails.\n\n#### RETOKEN\n\nStanding for REturnTOKEN, this port accepts a token to be used to\nretrieve what was stored in order for the returned object to replace it.\n\n#### CACHESIZE\n\nnoflo-lift does not have a cache limit as it expects you to finish\nprocessing on all opened requests. You may optionally set a cache size\nif you deal with asynchronous operations that may fail.\n\n\nOut Ports\n------------------------------\n\nnoflo-lift emits data via these ports:\n\n#### OUT\n\nThe data structure that has been processed and plugged back in is\nemitted to this port.\n\n#### EXTRACTED\n\nThe extracted data structure is emitted here. It is grouped at the\ntop-level by a token, which must group the processed data structure on\nreturn to the `RETURN` in port.\n\n#### EXTOKEN\n\nStanding for EXtractedTOKEN, this port emits the token when a\nsub-structure is extracted so Lift can identify which structure to\nreplace when a new sub-structure is returned.\n","readmeFilename":"README.md","_id":"noflo-lift@0.0.6","dist":{"shasum":"df0352513b2684c6a39aea893d45aeef85316dd5","tarball":"https://registry.npmjs.org/noflo-lift/-/noflo-lift-0.0.6.tgz","integrity":"sha512-44eEPNEJSC7MtkjFCwvGV4oEqg5hBTfirzWPImCxtgO6R6iUAWnZ0yPwX+lYSu1HXn5z1KE+zxPbIEwrJ24K9g==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCICpwTARP1nbxrtDhgSSlFu0+KcLETLv66P4mtK218c9mAiEA+KvEikkHMRiooArzi4LyFHJHbfSl9bAK7Kj6GRK6bLs="}]},"_from":".","_npmVersion":"1.2.18","_npmUser":{"name":"kenhkan","email":"kenhkan@gmail.com"},"maintainers":[{"name":"kenhkan","email":"kenhkan@gmail.com"}],"directories":{}},"0.0.7":{"name":"noflo-lift","description":"Lift Packets for Processing in NoFlo","keywords":["noflo","lift","extract","subset"],"author":{"name":"Kenneth Kan","email":"kenhkan@gmail.com"},"version":"0.0.7","licenses":[{"type":"MIT","url":"https://github.com/kenhkan/noflo-lift/blob/master/LICENSE.md"}],"engines":{"node":">=0.6.0"},"repository":{"type":"git","url":"git://github.com/kenhkan/noflo-lift"},"dependencies":{"noflo":"https://github.com/kenhkan/noflo/tarball/master","underscore":"1.4.x","underscore.string":"2.3.x","noflo-swiss":"0.0.x","noflo-flow":"0.0.x","noflo-groups":"0.0.x","noflo-packets":"0.0.x"},"devDependencies":{"coffeelint":"*","coffee-script":"1.6.x","noflo-test":"https://github.com/kenhkan/noflo-test/tarball/master"},"noflo":{"components":{"Extractor":"./components/Extractor.coffee","Assembler":"./components/Assembler.coffee"},"graphs":{"Lift":"./graphs/Lift.fbp"}},"scripts":{"pretest":"./node_modules/.bin/coffeelint -r components","test":"./node_modules/.bin/noflo-test --spec test/*.coffee"},"readme":"Lift Packets for Processing in NoFlo [](https://travis-ci.org/kenhkan/noflo-lift)\n===============================\n\nIn a [NoFlo](http://noflojs.org/) program, how the program processes\ndata is more important than the data structure. It is evident in that\nmost NoFlo programs expect a rather flat data structure of a series of\npackets enclosed in one or two levels of groups.\n\nWhen your program expects a more complex data structure, it is useful to\nbe able to extract a subset of the structure, do some work, and plug it\nright back into where it was extracted from. noflo-lift allows you to\nliterally \"lift\" a subset of the data structure by providing a pattern\nobject for further processing on just that one piece. It then accepts\nsome data structure that noflo-lift would then insert back in place.\n\n\nIn Ports\n------------------------------\n\nnoflo-lift accepts data via these ports:\n\n#### IN\n\nAny valid NoFlo data structure\n\n#### PATTERN\n\nA pattern is a path-like array denoting the group structure to extract.\nFor instance, in XML schematics, if you have an incoming data structure:\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\nAnd you want to extract just `GroupC` for processing, you would pass in,\nin JSON:\n\n [ \"GroupA\", \"GroupB\", \"GroupC\" ]\n\n#### RETURN\n\nThe processed data structure must be returned to this port to continue\nits journal through the `OUT` port. See the `PROCESS` out port for\ndetails.\n\n#### RETOKEN\n\nStanding for REturnTOKEN, this port accepts a token to be used to\nretrieve what was stored in order for the returned object to replace it.\n\n#### CACHESIZE\n\nnoflo-lift does not have a cache limit as it expects you to finish\nprocessing on all opened requests. You may optionally set a cache size\nif you deal with asynchronous operations that may fail.\n\n\nOut Ports\n------------------------------\n\nnoflo-lift emits data via these ports:\n\n#### OUT\n\nThe data structure that has been processed and plugged back in is\nemitted to this port.\n\n#### EXTRACTED\n\nThe extracted data structure is emitted here. It is grouped at the\ntop-level by a token, which must group the processed data structure on\nreturn to the `RETURN` in port.\n\n#### EXTOKEN\n\nStanding for EXtractedTOKEN, this port emits the token when a\nsub-structure is extracted so Lift can identify which structure to\nreplace when a new sub-structure is returned.\n","readmeFilename":"README.md","_id":"noflo-lift@0.0.7","dist":{"shasum":"0dd787e01985921d1dfbf91f9a8e4428d6a91593","tarball":"https://registry.npmjs.org/noflo-lift/-/noflo-lift-0.0.7.tgz","integrity":"sha512-WVN1cCSObZXpN0qH/pG9VrbM4gPGV7M+tHpR16x4jRG/31X/7jV9KYWwJ3+yQe0ZfoX4Ivy/WiOXMCev+uQuKg==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQD/qmWvTcrL602ye89MRQT6L+7hHlon91A7xAivtDNikgIgVWLsSZObJ7t8eOqOsgKELfobhjLyt5myZfprmGF1RbI="}]},"_from":".","_npmVersion":"1.2.18","_npmUser":{"name":"kenhkan","email":"kenhkan@gmail.com"},"maintainers":[{"name":"kenhkan","email":"kenhkan@gmail.com"}],"directories":{}},"0.0.8":{"name":"noflo-lift","description":"Lift Packets for Processing in NoFlo","keywords":["noflo","lift","extract","subset"],"author":{"name":"Kenneth Kan","email":"kenhkan@gmail.com"},"version":"0.0.8","licenses":[{"type":"MIT","url":"https://github.com/kenhkan/noflo-lift/blob/master/LICENSE.md"}],"engines":{"node":">=0.6.0"},"repository":{"type":"git","url":"git://github.com/kenhkan/noflo-lift"},"dependencies":{"noflo":"https://github.com/kenhkan/noflo/tarball/master","underscore":"1.4.x","underscore.string":"2.3.x","noflo-swiss":"0.0.x","noflo-flow":"0.0.x","noflo-groups":"0.0.x","noflo-packets":"0.0.x"},"devDependencies":{"coffeelint":"*","coffee-script":"1.6.x","noflo-test":"https://github.com/kenhkan/noflo-test/tarball/master"},"noflo":{"components":{"Extractor":"./components/Extractor.coffee","Assembler":"./components/Assembler.coffee"},"graphs":{"Lift":"./graphs/Lift.fbp"}},"scripts":{"pretest":"./node_modules/.bin/coffeelint -r components","test":"./node_modules/.bin/noflo-test --spec test/*.coffee"},"readme":"Lift Packets for Processing in NoFlo [](https://travis-ci.org/kenhkan/noflo-lift)\n===============================\n\nIn a [NoFlo](http://noflojs.org/) program, how the program processes\ndata is more important than the data structure. It is evident in that\nmost NoFlo programs expect a rather flat data structure of a series of\npackets enclosed in one or two levels of groups.\n\nWhen your program expects a more complex data structure, it is useful to\nbe able to extract a subset of the structure, do some work, and plug it\nright back into where it was extracted from. noflo-lift allows you to\nliterally \"lift\" a subset of the data structure by providing a pattern\nobject for further processing on just that one piece. It then accepts\nsome data structure that noflo-lift would then insert back in place.\n\n\nIn Ports\n------------------------------\n\nnoflo-lift accepts data via these ports:\n\n#### IN\n\nAny valid NoFlo data structure\n\n#### PATTERN\n\nA pattern is a path-like array denoting the group structure to extract.\nFor instance, in XML schematics, if you have an incoming data structure:\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\nAnd you want to extract just `GroupC` for processing, you would pass in,\nin JSON:\n\n [ \"GroupA\", \"GroupB\", \"GroupC\" ]\n\n#### RETURN\n\nThe processed data structure must be returned to this port to continue\nits journal through the `OUT` port. See the `PROCESS` out port for\ndetails.\n\n#### RETOKEN\n\nStanding for REturnTOKEN, this port accepts a token to be used to\nretrieve what was stored in order for the returned object to replace it.\n\n#### CACHESIZE\n\nnoflo-lift does not have a cache limit as it expects you to finish\nprocessing on all opened requests. You may optionally set a cache size\nif you deal with asynchronous operations that may fail.\n\n\nOut Ports\n------------------------------\n\nnoflo-lift emits data via these ports:\n\n#### OUT\n\nThe data structure that has been processed and plugged back in is\nemitted to this port.\n\n#### EXTRACTED\n\nThe extracted data structure is emitted here. It is grouped at the\ntop-level by a token, which must group the processed data structure on\nreturn to the `RETURN` in port.\n\n#### EXTOKEN\n\nStanding for EXtractedTOKEN, this port emits the token when a\nsub-structure is extracted so Lift can identify which structure to\nreplace when a new sub-structure is returned.\n","readmeFilename":"README.md","_id":"noflo-lift@0.0.8","dist":{"shasum":"334498031e295d70539cd817d152ee141a04d310","tarball":"https://registry.npmjs.org/noflo-lift/-/noflo-lift-0.0.8.tgz","integrity":"sha512-3NznTILEhx42W3a8h8EEKcpyG3t3NwzjCYuH+dVNCIs6mxqyhcIOb1e1tfGqWylrYhLWOQX5xf4Whry+kJRRoA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIHfK5fB42OXnNgLOCBvXdacPLUNTxFYY0IfL9ScHS63tAiEAqmsbxpfCYRSz5zV2oAKSRXcaEgzz4nFRuaayvIyPeLM="}]},"_from":".","_npmVersion":"1.2.18","_npmUser":{"name":"kenhkan","email":"kenhkan@gmail.com"},"maintainers":[{"name":"kenhkan","email":"kenhkan@gmail.com"}],"directories":{}},"0.0.9":{"name":"noflo-lift","description":"Lift Packets for Processing in NoFlo","keywords":["noflo","lift","extract","subset"],"author":{"name":"Kenneth Kan","email":"kenhkan@gmail.com"},"version":"0.0.9","licenses":[{"type":"MIT","url":"https://github.com/kenhkan/noflo-lift/blob/master/LICENSE.md"}],"repository":{"type":"git","url":"https://github.com/kenhkan/noflo-lift"},"dependencies":{"noflo":"~0.4.0","underscore":"1.4.x","underscore.string":"2.3.x","noflo-swiss":"0.0.x","noflo-flow":"0.0.x","noflo-groups":"0.0.x","noflo-packets":"0.0.x","noflo-test":"https://github.com/kenhkan/noflo-test/tarball/master"},"devDependencies":{"grunt-exec":"~0.4.2","grunt":"~0.4.1","grunt-contrib-coffee":"~0.6.6","grunt-coffeelint":"~0.0.6","grunt-cafe-mocha":"~0.1.2","chai":"~1.5.0","mocha":"~1.9.0","grunt-mocha-phantomjs":"~0.2.2","grunt-component-build":"~0.2.7","grunt-contrib-uglify":"~0.2.0","grunt-contrib-watch":"~0.3.1","component-json":"~0.1.4","grunt-combine":"~0.8.3","grunt-component":"~0.1.2","coffeelint":"*","coffee-script":"1.6.x","noflo-test":"~0.0.5"},"noflo":{"components":{"Extractor":"./components/Extractor.coffee","Assembler":"./components/Assembler.coffee"},"graphs":{"Lift":"./graphs/Lift.fbp"}},"readme":"# Lift Packets for Processing in NoFlo
[](http://travis-ci.org/kenhkan/noflo-lift) [](https://gemnasium.com/kenhkan/noflo-lift) [](http://badge.fury.io/js/noflo-lift) [](http://waffle.io/kenhkan/noflo-lift)\n\nIn a [NoFlo](http://noflojs.org/) program, how the program processes\ndata is more important than the data structure. It is evident in that\nmost NoFlo programs expect a rather flat data structure of a series of\npackets enclosed in one or two levels of groups.\n\nWhen your program expects a more complex data structure, it is useful to\nbe able to extract a subset of the structure, do some work, and plug it\nright back into where it was extracted from. noflo-lift allows you to\nliterally \"lift\" a subset of the data structure by providing a pattern\nobject for further processing on just that one piece. It then accepts\nsome data structure that noflo-lift would then insert back in place.\n\n\n## In Ports\n\nnoflo-lift accepts data via these ports:\n\n#### IN\n\nAny valid NoFlo data structure\n\n#### PATTERN\n\nA pattern is a path-like array denoting the group structure to extract.\nFor instance, in XML schematics, if you have an incoming data structure:\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\nAnd you want to extract just `GroupC` for processing, you would pass in,\nin JSON:\n\n [ \"GroupA\", \"GroupB\", \"GroupC\" ]\n\n#### RETURN\n\nThe processed data structure must be returned to this port to continue\nits journal through the `OUT` port. See the `PROCESS` out port for\ndetails.\n\n#### RETOKEN\n\nStanding for REturnTOKEN, this port accepts a token to be used to\nretrieve what was stored in order for the returned object to replace it.\n\n#### CACHESIZE\n\nnoflo-lift does not have a cache limit as it expects you to finish\nprocessing on all opened requests. You may optionally set a cache size\nif you deal with asynchronous operations that may fail.\n\n\n## Out Ports\n\nnoflo-lift emits data via these ports:\n\n#### OUT\n\nThe data structure that has been processed and plugged back in is\nemitted to this port.\n\n#### EXTRACTED\n\nThe extracted data structure is emitted here. It is grouped at the\ntop-level by a token, which must group the processed data structure on\nreturn to the `RETURN` in port.\n\n#### EXTOKEN\n\nStanding for EXtractedTOKEN, this port emits the token when a\nsub-structure is extracted so Lift can identify which structure to\nreplace when a new sub-structure is returned.\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/kenhkan/noflo-lift/issues"},"_id":"noflo-lift@0.0.9","dist":{"shasum":"b5dd3795ec63edd9ccb3ca31facfc7bceb08e114","tarball":"https://registry.npmjs.org/noflo-lift/-/noflo-lift-0.0.9.tgz","integrity":"sha512-7jTG5xmbfDELEEZMmzNnTZYKuFY259nwobjDtQre9IvU/cX22iSGn4Hl2iT/jfXCF4OT/miA/1IoE9uKfpl1pQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCUJ8wJ59CR6p3ilwpfV1O0RuvCwB84L20OOYuzdfHWdAIgJAGMwr4r754TF/5eMJz1Llc2O8MhtKZjZ064ch+wsc0="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"kenhkan","email":"kenhkan@gmail.com"},"maintainers":[{"name":"kenhkan","email":"kenhkan@gmail.com"}]},"0.0.10":{"name":"noflo-lift","description":"Lift Packets for Processing in NoFlo","keywords":["noflo","lift","extract","subset"],"author":{"name":"Kenneth Kan","email":"kenhkan@gmail.com"},"version":"0.0.10","licenses":[{"type":"MIT","url":"https://github.com/kenhkan/noflo-lift/blob/master/LICENSE.md"}],"repository":{"type":"git","url":"https://github.com/kenhkan/noflo-lift"},"dependencies":{"noflo":"~0.4.0","underscore":"1.4.x","underscore.string":"2.3.x","noflo-swiss":"0.0.x","noflo-flow":"~0.2.0","noflo-groups":"0.0.x","noflo-packets":"0.0.x","noflo-test":"https://github.com/kenhkan/noflo-test/tarball/master"},"devDependencies":{"grunt-exec":"~0.4.2","grunt":"~0.4.1","grunt-contrib-coffee":"~0.6.6","grunt-coffeelint":"~0.0.6","grunt-cafe-mocha":"~0.1.2","chai":"~1.5.0","mocha":"~1.9.0","grunt-mocha-phantomjs":"~0.2.2","grunt-component-build":"~0.2.7","grunt-contrib-uglify":"~0.2.0","grunt-contrib-watch":"~0.3.1","component-json":"~0.1.4","grunt-combine":"~0.8.3","grunt-component":"~0.1.2","coffeelint":"*","coffee-script":"1.6.x","noflo-test":"~0.0.5"},"noflo":{"components":{"Extractor":"./components/Extractor.coffee","Assembler":"./components/Assembler.coffee"},"graphs":{"Lift":"./graphs/Lift.fbp"}},"scripts":{"test":"grunt test"},"readme":"# Lift Packets for Processing in NoFlo
[](http://travis-ci.org/kenhkan/noflo-lift) [](https://gemnasium.com/kenhkan/noflo-lift) [](http://badge.fury.io/js/noflo-lift) [](http://waffle.io/kenhkan/noflo-lift)\n\nIn a [NoFlo](http://noflojs.org/) program, how the program processes\ndata is more important than the data structure. It is evident in that\nmost NoFlo programs expect a rather flat data structure of a series of\npackets enclosed in one or two levels of groups.\n\nWhen your program expects a more complex data structure, it is useful to\nbe able to extract a subset of the structure, do some work, and plug it\nright back into where it was extracted from. noflo-lift allows you to\nliterally \"lift\" a subset of the data structure by providing a pattern\nobject for further processing on just that one piece. It then accepts\nsome data structure that noflo-lift would then insert back in place.\n\n\n## In Ports\n\nnoflo-lift accepts data via these ports:\n\n#### IN\n\nAny valid NoFlo data structure\n\n#### PATTERN\n\nA pattern is a path-like array denoting the group structure to extract.\nFor instance, in XML schematics, if you have an incoming data structure:\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\nAnd you want to extract just `GroupC` for processing, you would pass in,\nin JSON:\n\n [ \"GroupA\", \"GroupB\", \"GroupC\" ]\n\n#### RETURN\n\nThe processed data structure must be returned to this port to continue\nits journal through the `OUT` port. See the `PROCESS` out port for\ndetails.\n\n#### RETOKEN\n\nStanding for REturnTOKEN, this port accepts a token to be used to\nretrieve what was stored in order for the returned object to replace it.\n\n#### CACHESIZE\n\nnoflo-lift does not have a cache limit as it expects you to finish\nprocessing on all opened requests. You may optionally set a cache size\nif you deal with asynchronous operations that may fail.\n\n\n## Out Ports\n\nnoflo-lift emits data via these ports:\n\n#### OUT\n\nThe data structure that has been processed and plugged back in is\nemitted to this port.\n\n#### EXTRACTED\n\nThe extracted data structure is emitted here. It is grouped at the\ntop-level by a token, which must group the processed data structure on\nreturn to the `RETURN` in port.\n\n#### EXTOKEN\n\nStanding for EXtractedTOKEN, this port emits the token when a\nsub-structure is extracted so Lift can identify which structure to\nreplace when a new sub-structure is returned.\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/kenhkan/noflo-lift/issues"},"_id":"noflo-lift@0.0.10","dist":{"shasum":"0404a30a21a5386bda39a0566c76da0190d74dd1","tarball":"https://registry.npmjs.org/noflo-lift/-/noflo-lift-0.0.10.tgz","integrity":"sha512-geNna0e/tMSJf91iqpafR6ztntaKy/cIjcroQcZels8P7Jkg2KUZJidbmHVLo8hLCi3xFM7k1oymJq01YIZOBQ==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCUKkSNjS57wUEGJSKrzU4mX+Fv4T2fEyvieq7jYFxvCgIgYCOvK7KCGVXWrrGHBuEFT+ekaH3KPROdrWbzrC+squU="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"kenhkan","email":"kenhkan@gmail.com"},"maintainers":[{"name":"kenhkan","email":"kenhkan@gmail.com"}]},"0.0.11":{"name":"noflo-lift","description":"Lift Packets for Processing in NoFlo","keywords":["noflo","lift","extract","subset"],"author":{"name":"Kenneth Kan","email":"kenhkan@gmail.com"},"version":"0.0.11","licenses":[{"type":"MIT","url":"https://github.com/kenhkan/noflo-lift/blob/master/LICENSE.md"}],"repository":{"type":"git","url":"https://github.com/kenhkan/noflo-lift"},"dependencies":{"noflo":"~0.4.0","underscore":"1.4.x","underscore.string":"2.3.x","noflo-swiss":"0.0.x","noflo-flow":"~0.2.0","noflo-groups":"0.0.x","noflo-packets":"0.0.x","noflo-test":"~0.0.6","nohoarder":"0.0.2","noflo-cache":"0.0.1"},"devDependencies":{"grunt-exec":"~0.4.2","grunt":"~0.4.1","grunt-contrib-coffee":"~0.6.6","grunt-coffeelint":"~0.0.6","grunt-cafe-mocha":"~0.1.2","chai":"~1.5.0","mocha":"~1.9.0","grunt-mocha-phantomjs":"~0.2.2","grunt-component-build":"~0.2.7","grunt-contrib-uglify":"~0.2.0","grunt-contrib-watch":"~0.3.1","component-json":"~0.1.4","grunt-combine":"~0.8.3","grunt-component":"~0.1.2","coffeelint":"*","coffee-script":"1.6.x","noflo-test":"~0.0.5"},"noflo":{"components":{"Extractor":"./components/Extractor.coffee","Assembler":"./components/Assembler.coffee"},"graphs":{"Lift":"./graphs/Lift.fbp"}},"scripts":{"test":"grunt test"},"readme":"# Lift Packets for Processing in NoFlo
[](http://travis-ci.org/kenhkan/noflo-lift) [](https://gemnasium.com/kenhkan/noflo-lift) [](http://badge.fury.io/js/noflo-lift) [](http://waffle.io/kenhkan/noflo-lift)\n\nIn a [NoFlo](http://noflojs.org/) program, how the program processes\ndata is more important than the data structure. It is evident in that\nmost NoFlo programs expect a rather flat data structure of a series of\npackets enclosed in one or two levels of groups.\n\nWhen your program expects a more complex data structure, it is useful to\nbe able to extract a subset of the structure, do some work, and plug it\nright back into where it was extracted from. noflo-lift allows you to\nliterally \"lift\" a subset of the data structure by providing a pattern\nobject for further processing on just that one piece. It then accepts\nsome data structure that noflo-lift would then insert back in place.\n\n\n## In Ports\n\nnoflo-lift accepts data via these ports:\n\n#### IN\n\nAny valid NoFlo data structure\n\n#### PATTERN\n\nA pattern is a path-like array denoting the group structure to extract.\nFor instance, in XML schematics, if you have an incoming data structure:\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\nAnd you want to extract just `GroupC` for processing, you would pass in,\nin JSON:\n\n [ \"GroupA\", \"GroupB\", \"GroupC\" ]\n\n#### RETURN\n\nThe processed data structure must be returned to this port to continue\nits journal through the `OUT` port. See the `PROCESS` out port for\ndetails.\n\n#### RETOKEN\n\nStanding for REturnTOKEN, this port accepts a token to be used to\nretrieve what was stored in order for the returned object to replace it.\n\n#### CACHESIZE\n\nnoflo-lift does not have a cache limit as it expects you to finish\nprocessing on all opened requests. You may optionally set a cache size\nif you deal with asynchronous operations that may fail.\n\n\n## Out Ports\n\nnoflo-lift emits data via these ports:\n\n#### OUT\n\nThe data structure that has been processed and plugged back in is\nemitted to this port.\n\n#### EXTRACTED\n\nThe extracted data structure is emitted here. It is grouped at the\ntop-level by a token, which must group the processed data structure on\nreturn to the `RETURN` in port.\n\n#### EXTOKEN\n\nStanding for EXtractedTOKEN, this port emits the token when a\nsub-structure is extracted so Lift can identify which structure to\nreplace when a new sub-structure is returned.\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/kenhkan/noflo-lift/issues"},"_id":"noflo-lift@0.0.11","dist":{"shasum":"da5a6013106c9b4dd9c32479f664bf386e6e3888","tarball":"https://registry.npmjs.org/noflo-lift/-/noflo-lift-0.0.11.tgz","integrity":"sha512-FLxTh3WNyu0XbvhxsBrIWQPv1PvqowIzDcXD1QJT97M69555tg+boS9qpBCls69RbqG+YUusSVXMGeP8IHNczA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIAuWb2ryXPlPTDb/raaNLlYF78gU6IbFV1fp0QmhnSFYAiAjh211D/OocZIkHUeHPbmVNZph16D2g7LDCnSaFwh6Qg=="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"kenhkan","email":"kenhkan@gmail.com"},"maintainers":[{"name":"kenhkan","email":"kenhkan@gmail.com"}]},"0.0.12":{"name":"noflo-lift","description":"Lift Packets for Processing in NoFlo","keywords":["noflo","lift","extract","subset"],"author":{"name":"Kenneth Kan","email":"kenhkan@gmail.com"},"version":"0.0.12","licenses":[{"type":"MIT","url":"https://github.com/kenhkan/noflo-lift/blob/master/LICENSE.md"}],"repository":{"type":"git","url":"https://github.com/kenhkan/noflo-lift"},"dependencies":{"noflo":"~0.4.0","underscore":"~1.4.0","underscore.string":"~2.3.0","noflo-swiss":"~0.0.1","noflo-flow":"~0.3.2","noflo-groups":"~0.0.1","noflo-packets":"~0.0.1","noflo-test":"~0.0.6","nohoarder":"~0.0.2","noflo-cache":"~0.0.1"},"devDependencies":{"grunt-exec":"~0.4.2","grunt":"~0.4.1","grunt-contrib-coffee":"~0.6.6","grunt-coffeelint":"~0.0.6","grunt-cafe-mocha":"~0.1.2","chai":"~1.5.0","mocha":"~1.9.0","grunt-mocha-phantomjs":"~0.2.2","grunt-component-build":"~0.2.7","grunt-contrib-uglify":"~0.2.0","grunt-contrib-watch":"~0.3.1","component-json":"~0.1.4","grunt-combine":"~0.8.3","grunt-component":"~0.1.2","coffeelint":"*","coffee-script":"1.6.x","noflo-test":"~0.0.5"},"noflo":{"components":{"Extractor":"./components/Extractor.coffee","Assembler":"./components/Assembler.coffee"},"graphs":{"Lift":"./graphs/Lift.fbp"}},"scripts":{"test":"grunt test"},"readme":"# Lift Packets for Processing in NoFlo
[](http://travis-ci.org/kenhkan/noflo-lift) [](https://gemnasium.com/kenhkan/noflo-lift) [](http://badge.fury.io/js/noflo-lift) [](http://waffle.io/kenhkan/noflo-lift)\n\nIn a [NoFlo](http://noflojs.org/) program, how the program processes\ndata is more important than the data structure. It is evident in that\nmost NoFlo programs expect a rather flat data structure of a series of\npackets enclosed in one or two levels of groups.\n\nWhen your program expects a more complex data structure, it is useful to\nbe able to extract a subset of the structure, do some work, and plug it\nright back into where it was extracted from. noflo-lift allows you to\nliterally \"lift\" a subset of the data structure by providing a pattern\nobject for further processing on just that one piece. It then accepts\nsome data structure that noflo-lift would then insert back in place.\n\n\n## In Ports\n\nnoflo-lift accepts data via these ports:\n\n#### IN\n\nAny valid NoFlo data structure\n\n#### PATTERN\n\nA pattern is a path-like array denoting the group structure to extract.\nFor instance, in XML schematics, if you have an incoming data structure:\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\nAnd you want to extract just `GroupC` for processing, you would pass in,\nin JSON:\n\n [ \"GroupA\", \"GroupB\", \"GroupC\" ]\n\n#### RETURN\n\nThe processed data structure must be returned to this port to continue\nits journal through the `OUT` port. See the `PROCESS` out port for\ndetails.\n\n#### RETOKEN\n\nStanding for REturnTOKEN, this port accepts a token to be used to\nretrieve what was stored in order for the returned object to replace it.\n\n#### CACHESIZE\n\nnoflo-lift does not have a cache limit as it expects you to finish\nprocessing on all opened requests. You may optionally set a cache size\nif you deal with asynchronous operations that may fail.\n\n\n## Out Ports\n\nnoflo-lift emits data via these ports:\n\n#### OUT\n\nThe data structure that has been processed and plugged back in is\nemitted to this port.\n\n#### EXTRACTED\n\nThe extracted data structure is emitted here. It is grouped at the\ntop-level by a token, which must group the processed data structure on\nreturn to the `RETURN` in port.\n\n#### EXTOKEN\n\nStanding for EXtractedTOKEN, this port emits the token when a\nsub-structure is extracted so Lift can identify which structure to\nreplace when a new sub-structure is returned.\n","readmeFilename":"README.md","bugs":{"url":"https://github.com/kenhkan/noflo-lift/issues"},"_id":"noflo-lift@0.0.12","dist":{"shasum":"539c89058c9e0c0a4b057a69b29c60be9b5d3726","tarball":"https://registry.npmjs.org/noflo-lift/-/noflo-lift-0.0.12.tgz","integrity":"sha512-v4/PN4M/Zn9dB5yPRpZhLEN1nyMQnrXqoH/4Z4Ts0Rshp4Ybsd6UIL18iKEOmZbWoUeWJJcoZDp6i30NgYsNAA==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIDSj253/80EhbnGwDhmfaQdiP8Qkd00gBwOjcJ3cgv8uAiEA91A0z77OtEbKUTpdfh7nvZp/LEcwr9+ijWfuIjwahyY="}]},"_from":".","_npmVersion":"1.3.8","_npmUser":{"name":"kenhkan","email":"kenhkan@gmail.com"},"maintainers":[{"name":"kenhkan","email":"kenhkan@gmail.com"}]}},"readme":"Lift Packets for Processing in NoFlo [](https://travis-ci.org/kenhkan/noflo-lift)\n===============================\n\nIn a [NoFlo](http://noflojs.org/) program, how the program processes\ndata is more important than the data structure. It is evident in that\nmost NoFlo programs expect a rather flat data structure of a series of\npackets enclosed in one or two levels of groups.\n\nWhen your program expects a more complex data structure, it is useful to\nbe able to extract a subset of the structure, do some work, and plug it\nright back into where it was extracted from. noflo-lift allows you to\nliterally \"lift\" a subset of the data structure by providing a pattern\nobject for further processing on just that one piece. It then accepts\nsome data structure that noflo-lift would then insert back in place.\n\n\nIn Ports\n------------------------------\n\nnoflo-lift accepts data via these ports:\n\n#### IN\n\nAny valid NoFlo data structure\n\n#### PATTERN\n\nA pattern is a path-like array denoting the group structure to extract.\nFor instance, in XML schematics, if you have an incoming data structure:\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\nAnd you want to extract just `GroupC` for processing, you would pass in,\nin JSON:\n\n [ \"GroupA\", \"GroupB\", \"GroupC\" ]\n\n#### RETURN\n\nThe processed data structure must be returned to this port to continue\nits journal through the `OUT` port. See the `PROCESS` out port for\ndetails.\n\n#### CACHESIZE\n\nnoflo-lift does not have a cache limit as it expects you to finish\nprocessing on all opened requests. You may optionally set a cache size\nif you deal with asynchronous operations that may fail.\n\n\nOut Ports\n------------------------------\n\nnoflo-lift emits data via these ports:\n\n#### OUT\n\nThe data structure that has been processed and plugged back in is\nemitted to this port.\n\n#### PROCESS\n\nThe *extracted* data structure is emitted here. It is grouped at the\ntop-level by a token, which must group the processed data structure on\nreturn to the `RETURN` in port.\n","maintainers":[{"name":"kenhkan","email":"kenhkan@gmail.com"}],"time":{"modified":"2022-06-22T04:24:50.802Z","created":"2013-04-22T21:33:26.913Z","0.0.1":"2013-04-22T21:33:33.310Z","0.0.3":"2013-04-23T08:39:09.622Z","0.0.4":"2013-04-23T19:33:39.012Z","0.0.5":"2013-05-01T22:10:37.857Z","0.0.6":"2013-05-03T00:59:03.607Z","0.0.7":"2013-05-03T05:16:12.048Z","0.0.8":"2013-06-09T02:47:54.352Z","0.0.9":"2013-09-09T23:43:23.041Z","0.0.10":"2013-09-12T02:07:44.071Z","0.0.11":"2013-09-14T11:23:30.310Z","0.0.12":"2013-09-18T03:33:01.990Z"},"author":{"name":"Kenneth Kan","email":"kenhkan@gmail.com"},"repository":{"type":"git","url":"https://github.com/kenhkan/noflo-lift"}}