The approach sounds good, but trying out I run into a very basic problem:
With one of the normal functions I have this naming:
"type": "function",
"z": "b25c3ffa5d02edb9",
"g": "a24f59ac4513cf4b",
"name": "filter open/xyz",
With all "normal" NR there is no problem with this naming, but with functions-templates-watch.js it throws an error like this:
$ node functions-templates-watch
Extracting from flows.json
Watching /home/user/.node-red/src and flows.json
node:fs:2367
return binding.writeFileUtf8(
^
Error: ENOENT: no such file or directory, open '/home/user/.node-red/src/base_explorer/filter open/ecu-d2009fae2476ec04.js'
at Object.writeFileSync (node:fs:2367:20)
Seems the functionality needs a specific naming convention.
Doesn't sound good because "filter open3e/ecu" is the naming of a normal function in a normal flow.
