Henri Bergius
Henri Bergius
Sounds like a good idea. I'll see when I have time to add this. Theoretically we could even use KReS (http://wiki.iks-project.eu/index.php/KReS) to generate the default validation rules.
See a bit more comprehensive description of how this should be handled in #34
@neogermi idea: how about allowing developers to attach a custom `validate` callback to a type? Then VIE could run those of each of an entity's types as an implementation of...
VIE's type system already has some rudimentary information that can be used for validation. For each registered type we have a set of known properties. For these properties we have:...
Note: Merged into #12
MQTT could be another interesting possibility http://mqtt.org/ Their ideas page for auto-discovery: http://mqtt.org/wiki/doku.php/broker_auto-discovery
You may want to take a look at noflo/noflo#90 for some subtle points related to this, for example regular port vs. ArrayPort
https://xdk.bosch-connectivity.com/ is a nice device with tons of sensors
Also, component template in https://github.com/noflo/noflo-ui/blob/master/runtimeinfo/microflo.yaml
Once we have this in place, it might make sense to have a CI/CD process for NoFlo component libraries that would publish their component files and a `fbp.json` on GitHub...