error or warn on config file typos #108
Description
Currently, it is valid for a configuration file to contain configuration of nodes which do not exist in any stream/connection/etc. This bit me because I'd changed the name of a node and not updated the config, reverting it to defaults. I don't know hard it is to check, but it seems like it would be very helpful if there were at least a warning in the event of there being node configurations that don't actually correspond to a node being created.