Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How do * inputs (and outputs?) work? #8

Open
tlrobinson opened this issue Dec 3, 2012 · 0 comments
Open

How do * inputs (and outputs?) work? #8

tlrobinson opened this issue Dec 3, 2012 · 0 comments

Comments

@tlrobinson
Copy link
Member

In the formatter block it looks like we assume there is a "*" property on the input object, which is itself an object containing arbitrary keys.

I assumed "" would just be a signal to pipeline editors that any extra properties were allowed (maybe only of a specific type?), and there wouldn't actually be a "" property in the requests/responses.

A framework like node-webpipe could split any undeclared properties into a separate object for convenience. I think this would simplify some things, like the pipeline executors.

Also, does it make sense to have "" outputs? In my pipeline editor I have two pseudo-blocks representing the inputs and outputs for the pipeline (if any). The inputs psuedo-block has a "" output that lets you add new pipeline inputs. But does it make sense for normal blocks? It may make sense if we eventually have other pipeline styles that pipe around whole records rather than values (similar to Storm, maybe)

Discuss.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant