From a049bc67f8f6433e51c8cc16314b46541339ecef Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nathana=C3=ABl=20L=C3=A9caud=C3=A9?= Date: Mon, 15 May 2017 10:35:22 -0400 Subject: [PATCH] Updated Design: external file for function and templates nodes (markdown) --- Design:-external-file-for-function-and-templates-nodes.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Design:-external-file-for-function-and-templates-nodes.md b/Design:-external-file-for-function-and-templates-nodes.md index 08256c8..080e24d 100644 --- a/Design:-external-file-for-function-and-templates-nodes.md +++ b/Design:-external-file-for-function-and-templates-nodes.md @@ -10,4 +10,6 @@ We know some third party nodes do this but we think this should be integrated in We propose the addition of a checkbox named `Load from external file` just above the code field. Checking this checkbox would make a field appear where the user can type the path to a file, similar to the `file-in` node. Given the fact some cloud environment are not compatible with a traditional file system, a setting named `allowExternalFiles` could be added in `settings.js` to disable this feature entirely. ## Exporting flows -This brings one problem, what happens when someone exports a flow ? We propose the addition of a checkbox in the flow export dialog named `Embed external files` that would embed the external file contents within the exported flow making sharing of that flow possible. \ No newline at end of file +This brings one problem, what happens when someone exports a flow ? We propose the addition of a checkbox in the flow export dialog named `Embed external files` that would embed the external file contents within the exported flow making sharing of that flow possible. + +Another possibility would be to have some sort of `Export project` option that would export a zip file containing the flow file, settings.js, lib folder and external files. \ No newline at end of file