Skip to content

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

@tlrobinson

Description

@tlrobinson

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions