Hello,
As a user i would like to set extra properties to a flow.
Does NodeRED allows it?
Hi Backboard7880 & welcome to the forum.
No, but I am am curious as to why?
Thanks for the quick answer.
I would like to add meta data to the flow to indicate its dependencies on other flows.
Here is how I got here.
Let's say I have flow A, B, and C. They all perform some calculations and get their respective set of input.
the output of flowA is the input of flowB.
the output of flowB is the input of flowC.
I have a web service that would figure out the dependency tree and sequencially run each flows as its collecting the required inputs.
web service reads all the flows
web service resolves that A is the starting point.
web service runs A then goes through the dependency tree until the final output.
Ok, while I cannot understand why anyone would require this level of abstraction, added complication & non visual routing when you could achieve the same thing with flow routing (switch nodes) and msg properties, I think your only option at this point is to use a structured data (JSON / XML) in the description field.
It is actually possible to register custom edit panes in the edit dialog. It's a currently undocumented feature that was fairly recently added. I can dig out an example if you are really interested.
However, we don't provide any way to add custom properties directly to a node or the flow - so I suspect its only half of what you're looking for. Being able to add custom properties to things is something in the backlog, but it's a big backlog and this it is a very niche feature so hasn't had any real attention.
An alternative approach would be for you to register a custom configuration node, and then dynamically add one to each flow when you have metadata to store. The Node-RED Dashboard set of nodes does something similar - it adds a ui_base config node to store the dashboard configuration.
Thanks @knolleary I would like to see that example when you get a chance.
I'll also give it a shot with the custom configuration node.
it's one of my requirements to have the overarching flow that combines A,B,C not statically wired together. And at the same time enjoy the LoCode interface for the small stand-alone flows.
Also one of the ideas around the group feature for nodes was to allow them to be visually grouped - but then also at some point to have group properties which could indicate separation or other interfaces.
There is an example in uibuilder.
Thanks this answers the question.
Not sure that does answer the question. That shows the UI builder node has tabs within its configuration pane - something any node could do already.
That is not the same as adding a custom pane to the Flow edit dialog which was the original question.
@knolleary I had a look at it earlier today and no, the UI builder is not what I was looking for.
