node-red/red
Nick O'Leary d148a23ed6 Handle config nodes appearing out of order in flow
The editor ensures config nodes appear first in the flow file. The
code in the runtime and editor assumes this to be the case, so that
when a node is instantiated that requires a config node, it can assume
the config node already exists.

This change allows a config node to appear in the flow file after a
node that wants to use it. In both the editor and runtime, the code
now scans for config nodes and handles them first.
2015-02-24 23:04:55 +00:00
..
api Allow palette categories to be predefined 2015-02-06 13:16:19 +00:00
nodes Handle config nodes appearing out of order in flow 2015-02-24 23:04:55 +00:00
storage Increase unit test coverage of auth code 2015-02-05 13:00:56 +00:00
comms.js Increase unit test coverage of auth code 2015-02-05 13:00:56 +00:00
events.js Start to add server-side events 2013-09-09 20:03:22 +01:00
log.js Add Log.trace/debug/error functions 2015-02-05 17:05:39 +00:00
red.js Tie auth middleware to needsPermission api 2015-02-05 23:43:35 +00:00
server.js revert small whitespace change to server start messages. 2015-02-24 22:22:16 +00:00
settings.js Add permissions and user menu 2015-02-05 13:00:55 +00:00
util.js Identify modified nodes on deploy 2015-01-15 10:28:10 +00:00