node-red-contrib-publishflows
Advanced tools
Comparing version 0.0.1 to 0.0.2
{ | ||
"name": "node-red-contrib-publishflows", | ||
"version": "0.0.1", | ||
"version": "0.0.2", | ||
"description": "PublishFlows allows projects to use other project parts as dependencies.", | ||
@@ -5,0 +5,0 @@ "author": "Stephen J. Carnam <steveorevo@gmail.com>", |
@@ -163,5 +163,7 @@ module.exports = function(RED) { | ||
var pf = RED.settings.functionGlobalContext.get("publishflows"); | ||
pf.forEach(function(p) { | ||
man.publishFlows.push(S(p.path).getRightMost("/").toString()); | ||
}); | ||
if (typeof pf != "undefined") { | ||
pf.forEach(function(p) { | ||
man.publishFlows.push(S(p.path).getRightMost("/").toString()); | ||
}); | ||
} | ||
resolve(man); | ||
@@ -168,0 +170,0 @@ } |
@@ -28,3 +28,3 @@ # node-red-contrib-publishflows | ||
A project that lists another project as a dependency will automatically have | ||
it's predefined components (tabs, subflows, arbitrary asset files) merged into | ||
its predefined components (tabs, subflows, arbitrary asset files) merged into | ||
the current project; overwriting/updating any existing nodes that share the | ||
@@ -74,3 +74,3 @@ same I.D. | ||
 | ||
 | ||
@@ -84,3 +84,3 @@ Because the [pf-test](http://github.com/steveorevo/pf-test) project is hosted on github.com, we can use NodeJS' | ||
 | ||
 | ||
@@ -97,8 +97,20 @@ Master refers to the main development branch in the github repo. However, you can | ||
You can distinguish dependencies that use the PublishFlows node from other dependencies as | ||
they will appear with a different **(3)** green tinted icon. If all goes well, you should | ||
they will appear with a different **(3)** green tinted and pyramid cubed icon. If all goes well, you should | ||
now see the "Test Subflow" node in your project's sidebar. You've just created a project | ||
that uses another project as a dependency. | ||
 | ||
 | ||
### Removing a PublishFlows Project Dependency | ||
PublishFlows makes it easy to remove a PublishFlows based project dependency. Simply use Node-RED's native | ||
"remove from project" button under the dependencies panel of the project's settings. You | ||
will be prompted with a Node-RED confirmation dialog with three options: Cancel, Keep, and | ||
Remove. **Cancel**, simply ignores the operation. **Keep** allows you to keep the flows and/or files | ||
that were imported prior in the "merge publishflows" operation while removing the dependency | ||
listing in your package.json file. Lastly, **Remove** removes both the dependency from your project's | ||
package.json file and scans the dependency's manifest file to remove any assets (flows and/or files) | ||
from your current project. | ||
 | ||
## What to Publish | ||
@@ -105,0 +117,0 @@ A PublishFlows project should only publish elements that it wishes to furnish to |
978512
492
139