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

Dummy component support #593

Open
bergie opened this issue Feb 23, 2018 · 1 comment
Open

Dummy component support #593

bergie opened this issue Feb 23, 2018 · 1 comment
Milestone

Comments

@bergie
Copy link
Member

bergie commented Feb 23, 2018

Right now we only support starting a network if all components used inside it are actually available and runnable.

However, there is certain amount of demand for having partially-implemented graphs, for example with Flowhub and top-down design (noflo/noflo-ui#266). In this case we'd want to instantiate "dummy" (no-op) components for the graph nodes that don't yet have an implementation, and otherwise run the network normally. Messages received by these no-op components could either raise an error, or be ignored.

Potential implementation for dummy components could be based on the MsgFlo foreign participant format where you can define things like ports.

@bergie bergie added this to the NoFlo 2.0 milestone Dec 7, 2020
@bergie
Copy link
Member Author

bergie commented Dec 29, 2020

We can use the # @runtime annotation to distinguish NoFlo dummies from MsgFlo foreign participants

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