Is there a way to configure Node-RED to create separate flow.json files - one for each "flow" (aka tab) within the set of flows for a given Node-RED Git enabled project? The reason being is that as an overall flow gets large it is convenient to be able to move a set of nodes to a specific flow/tab within the overall Node-RED project (as is currently supported). However, when this is done Node-RED still saves all of flows configuration to a single flow.json file (instead a separate .json file for each flow). From the Git version control perspective, effectively the entire program's "code" lives in a single file - which can get very large. Several benefits would be provided, from a Git perspective, if each distinct flow/tab was saved into its own file (e.g. smaller individual flow files, version history per flow, easier multi-user team development - e.g. each team member responsible for a specific flow file, etc.)
If this can't be done today could this feature be considered? For example, allow the settings.js file to optionally have Node-RED save each flow/tab to a separate file - with perhaps the master flow.json file pointing to each of the individual flow files. Thanks.
PS - I used to develop with Microsoft LightSwitch (now discontinued btw) which was similar to Node-RED in that it was RAD tool with a visual dev interface that would automatically generate program "code" - in their case it was XML. With the first version of LightSwitch the application would write all the "code" to a single file - but eventually based on feedback (specifically regarding the size of the "code" file and to also facilitate multi-user project development) Microsoft enhanced LightSwitch so that each distinct screen would be written to its own file.