There was a post last night which touched upon nodes saving their own context data, which would then be retrieved if node-RED was restarted, a full deploy, or a system reboot.
I'll use the ui chart node as an example, where currently if we want persistence, we need to add a change node to the flow to save the context, and an inject node to inject the context data back after a reboot. It's not a big deal (if you know how to do it), but couldn't this be rolled into the node as a config option? It would make it much easier for new users, and also simplify flows.
The same applies to many other nodes, which unless the user manages persistance, their state/data could be lost.
Some time ago, I raised this with @drmibell in relation to his excellent
node-red-contrib-simple-gate, and he kindly integrated the feature into the node config, so all users need to do, to ensure persistence is to tick the box. It works extremely well, and has never let me down!
I believe that Mike added the feature here, and this is the node's config;
I realise that developers are free to develop nodes how they wish, and if they don't want a particular feature, then that's fair enough - it's their node! My point in airing this is to ask what other members think? I got the impression that @dceejay was opposed to this suggestion, but I'm failing to see why....