Stephen McLaughlin

Hi all, in the interest of node-red and understanding the problem (from a point of view of "should we fix this in node-red") I did a fork and created a...

@bundabrg thanks for letting us know. Hopefully @Steveorevo can look at getting a fix published to npm sooner as more people test the PR

Hi @Steveorevo > I can tell that this will break the documentation for the [invoke example](https://github.com/Steveorevo/node-red-contrib-actionflows/blob/master/actionflows/demo/invoke.json). But not sure if > > `ContextStore.get('actionflows');` > > can be/is accessible from within...

@Steveorevo - regarding your comment... > @SandeepAgarwal13 "As a user who is invested heavily into the dynamic invoke functionality...", just to clarify; if we move forward with the PR, dynamic...

@Steveorevo Good stuff. Not sure if you are aware but the flows library does not auto update from NPM any more (hasn't done for quite some time). ~~You need to...

@hemantasapkota what is the chances you could share the changes you made to make this mobile friendly?

To minimise the need for future changes to NR src should this be a setting choice (i.e. permit user to specify key type, but default it to `ed25519`)? Alternatively, if...

Do you think it would be beneficial to also add an output to the email node? That way a flow msg can carry on and take appropriate actions based on...

@dceejay thats partly why i suspect adding an output would be more beneficial.

@kazuhitoyokoi Regarding using the complete node to pass a msg further downstream is (graphically) not really a "flow". The complete node only has a **non-visual** connection to the source node...