Yeah I noticed the 'z' association. So how is an export done by the editor? Does the export code handle the exceptions you noted above?
Since I just need the bulk of the flow to calculate a check sum... What you reference should be sufficient. This not going to be archival solution, just an audit process so I can keep the flow deployment consistent.
Still plan to put version # in the tab label, so the check sum is a extra safe guard if I happen to update a flow on some device and forget to archive it in my flow repo. Figure I will throw a alert window or something when the checksums don't match, i.e. the sum of the local flow and the sum of the official copy of the flow in my DB.
Of course, for archival I still have the script I wrote to capture the .node-red directory files applicable to recovery.
