From c2ccd8562e5328f9fff66a1bb3a4b357d6ce4ef4 Mon Sep 17 00:00:00 2001 From: hbeeken Date: Mon, 3 Nov 2014 02:54:06 -0800 Subject: [PATCH] Updated Node Design Guidelines (markdown) --- Node-Design-Guidelines.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/Node-Design-Guidelines.md b/Node-Design-Guidelines.md index 7550eff..fddab26 100644 --- a/Node-Design-Guidelines.md +++ b/Node-Design-Guidelines.md @@ -1,6 +1,3 @@ -### Messages -* [Message property conventions](https://github.com/node-red/node-red/wiki/Node-msg-Conventions) - ### Nodes There are three types of node. @@ -9,6 +6,13 @@ There are three types of node. - a **Function node** sits in the middle of a flow. It performs actions based on the incoming messages and passes on the resulting messages. One sub-type of Function node is a **Query node** that is used to retrieve data from an external API, such as a database query or a web services call. - an **Output node** sits at the end of a flow. It consumes the incoming messages and triggers an action. +### Conventions +(under development) +* [Message property conventions](https://github.com/node-red/node-red/wiki/Node-msg-Conventions) + +- data in the node settings overwrites that in an incoming message +- If data in the incoming message is not valid, the node should......? (Question: in this case should the node issue a warning? or an error? and/or change its status? or ignore this silently?) + --- Work in progress: