Just like CoffeeLint and jshint for component source code (#271), we should build and integrate a "graphlint" tool that would check and inform user on:
Unattached required ports
Datatype mismatches between ports
Possible other gotchas (incompatible firing patterns, group handling, etc)
The information needed for this is the graph(s), and the component library
Probably need to communicate more info about the components across FBP protocol. And will need to have per-runtime linting rules, since component/network behavior is different for each.
Just like CoffeeLint and jshint for component source code (#271), we should build and integrate a "graphlint" tool that would check and inform user on:
The information needed for this is the graph(s), and the component library