examples: parallel map

[francescoagati]

hi,
there is an example of parallel map node implementation?

something like this https://flows.nodered.org/node/node-red-contrib-wait-paths

[GabiGrin]

hey @francescoagati, sorry this took so long!
In Flyde this works out of the box; if a part has 2 different inputs, and they are not optional, it'll wait for both inputs to receive data before continuing.
You can see this live in https://www.flyde.dev/playground/bmi/ - it waits for both prompts to finish before executing. It would do that even if they were async.
You can change the code to return a delayed promise and see that in action

1. double click one of the prompts
2. enter

new Promise(
    res => setTimeout(
        () => res(prompt('What is your height (in cm)?'))
    ), 10000
)

And see if it will wait the full 10 seconds before continuing.

If you need more advanced behavior you can write a custom part. Until better documentation exists you can check any of the standard library parts at https://github.com/FlydeHQ/flyde/tree/main/stdlib/parts

And as I'm not experienced with https://flows.nodered.org/node/node-red-contrib-wait-paths, if you mean something else please let me know and I'll provide an example :)

[GabiGrin]

Hey @francescoagati, I've made many improvements to the extension since, and one of them being a few templates to choose from, one of them looping through the responses of 2 API calls and merging them into a new object:

If you try it, let me know what you think!

[francescoagati]

hey thanks,
i have try but i get this error with a simple flow

ode_modules/@flyde/resolver/dist/resolver/resolve-dependencies/resolve-dependencies.js:37
const refPartIds = part.instances
^
TypeError: Cannot read property 'instances' of undefined

with this code

const {loadFlow} = require('@flyde/runtime');
const executeFlow = loadFlow('./hello.flyde');
executeFlow() // executeFlow can also receive inputs, and other advanced configuration, more on that in the next steps
.then(({message}) => console.log(message))

[GabiGrin]

Hey @francescoagati, thanks for trying out that quick!
Please try:

const {loadFlowByPath} = require('@flyde/runtime');
const executeFlow = export function loadFlowByPath<Inputs>(
('./hello.flyde');

Docs need some update after the latest major refactoring :)

Also, .then(({message}) => console.log(message)). won't work.
You can try:

const executeFlow = loadFlowByPath('hello.flyde');
const result  = executeFlow({} ,{
    onOutputs: (outputs,data) => {
        console.log('............')
        console.log(outputs);
        console.log(data);

    }
})

Flyde required users to explicitly say what output pins cause the part to be completed (see https://www.flyde.dev/docs/lifecycle/). I've now added implicit completion, which the templates use, but it broke the output generation. Going to fix that soon!

[GabiGrin]

@francescoagati forgot to update that a fix was published

looking forward for your feedback and thanks for the patience in such an early stage of the project :)