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

fns allowed as the head of a flow? #3

Open
gjw opened this issue Feb 23, 2024 · 1 comment
Open

fns allowed as the head of a flow? #3

gjw opened this issue Feb 23, 2024 · 1 comment

Comments

@gjw
Copy link

gjw commented Feb 23, 2024

I'm probably just missing something, but it seems that all heads (sources) of a flow have to be static data?

Assume I have 2 heads in a flow: url and current-timestamp, and a single sink where they get mangled and printed.
I can put a dummy block with static data as the head before the timestamp to kick it off, but that's just a goofy workaround.

It makes sense, being reactive, that something needs to trigger current-timestamp, or it just fires never, or randomly.

It kind of makes sense to have the flow url -> timestamp -> output, except then you have to change the signature for timestamp to accept nonsense and pass the original data back out.

I guess you could

:connections {:url :output 
              :url  :timestamp
              :timestamp :output
              :output :done}

Then the only weirdness is the modified signature for timestamp. What's the suggested pattern here?

@gjw
Copy link
Author

gjw commented Feb 23, 2024

I think I just want to differentiate, logically and visually, between 'B is invoked when A completes' and 'B is invoked with A's output'

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