bigml-nodered
Version:
BigML bindings for Nodered
130 lines (115 loc) • 4.57 kB
HTML
<style>
.bigml_node_label { fill: white; }
#palette-BigML .palette_node { color: white; }
#red-ui-palette-BigML .red-ui-palette-label { color: white; }
</style>
<script type="text/javascript">
RED.nodes.registerType('reify', {
category: 'BigML',
color: '#454957',
defaults: {"name":{"value":"Reify","required":true},"input_keypath":{"value":""},"output_keypath":{"value":""},"reify":{"value":true}},
inputs:1,
outputs:1,
inputLabels: 'json',
outputLabels: 'result',
icon: 'icon_generic.png',
label: function() {
return this.name || 'Reify';
},
labelStyle: function() {
return this.name?"bigml_node_label":"";
},
});
</script>
<script type="text/x-red" data-template-name="reify">
<div class="form-row">
<label for="node-input-name">
<i class="icon-tag"></i> Name
</label>
<input type=text id=node-input-name value='Reify'>
</div>
<div class="form-row">
<label for="node-input-input_keypath">
<i class="icon-tag"></i> Input keypath
</label>
<input type=text id=node-input-input_keypath >
</div>
<div class="form-row">
<label for="node-input-output_keypath">
<i class="icon-tag"></i> Output keypath
</label>
<input type=text id=node-input-output_keypath >
</div>
<div class="form-row">
<label for="node-input-reify">
<i class="icon-tag"></i> Reify
</label>
<input type=checkbox id=node-input-reify value='true'>
</div>
</script>
<script type="text/html" data-help-name="reify">
<p>This is a BigML Nodered node.</p>
<h3>Details</h3>
<p>This node support all inputs defined in
<a href='https://bigml.com/api/reifys' target=blank>BigML REST
API</a>. By default, it expects to receive
a <code>json</code> input (see below for more details) and
it will output the <code>result</code> field of the created
resource.
</p>
<p>However, you can override default inputs and outputs by defining
the node port label so they match the desired input or output as
specified below.</p>
<p>Only when the node is used with the <code>reify</code> option
enabled, it will actually hit BigML and do its work there. This
generally means some resources will be created and sent through as
node outputs.</p>
<p>When the node is used with the <code>reify</code>option disabled,
it will generate WhizzML code and send it through to the next node
in the flow without hitting BigML. All WhizzML code created by this
node (and others) when not in <code>reify</code> mode is accumulated
and executed as a single WhizzML script by the first
downstream <code>reified</code> node.</p>
<h3>Inputs</h3>
<dl class="message-properties">
<dt>Name
<span class="property-type">:text</span>
</dt>
<dd></dd>
<dt>Input keypath
<span class="property-type">:text</span>
</dt>
<dd>A keypath used to extract a BigML resource ID from the
incoming payload. The corresonding resource will be fetched
from BigML.</dd>
<dt>Output keypath
<span class="property-type">:text</span>
</dt>
<dd>A keypath used to filter in only a property of the retrieved resource JSON.</dd>
<dt>Reify
<span class="property-type">:boolean</span>
</dt>
<dd>This node will GET the resource specified via
its <code>Input keypath</code> input and will output
the <code>Output keypath</code> from the resource
JSON. In addition, this node will execute the WhizzML
code generated at this (and upstream) node(s). You need
to enable this option if you want to get a result from
your flow that you can pass to a non-BigML node.</dd>
</dl>
<h3>Outputs</h3>
<ol class="node-ports">
<dl class="message-properties">
<dt>payload <span class="property-type">string or
JSON</span></dt>
<dd>the <code>result</code> of the created
BigML entity.</dd>
<dt>whizzml <span class="property-type">string</dt>
<dd>(only for <code>reified</code> nodes) the
generated WhizzML code which is fed into the next
node.
<dt>wzStack <span class="property-type">object</dt>
<dd>(only for <code>reified</code> nodes) private.
</dl>
</ol>
</script>