Hi there
this is an idea for a project but there isn't an "I have an Idea" category.
So having created Browser-Red the serverless Node-RED and Erlang-Red the Erlang backed Node-RED editor, I've been playing around with the flow editor for a while now. I have basically implemented the flow editor API twice now - once in the browser and once in Erlang
My idea is this: to encourage more XYZ-Red (i.e. Python-Red, Rust-Red, Lisp-Red, Node-RED-Red, etc), is to formally define the APIs required for driving the flow editor front end, i.e. clearly define a set of minimal required APIs to get the flow editor working.
Some of them are defined in this flow and some in the browser link above.
The aim would be to do enough so that that the flow editor can "deploy" a flow to the server (i.e. send the flows as json to the server and get "ok" response back). With the OpenAPI specification, it should be possible to set up a basic "flow receiver" backend from where the developer could parse and implement the nodes in the flows.json ....
