This PR adresses issues #26 #19 and #16 - as far as I agree with it.
In detail:
We move the pipeline metrics into a status light which is green when the last error is more than 5 cycles ago and red otherwise. Hover to get the complete information as a tooltip.
I suggest keeping the naming scheme as is (with underscores) and also display it as is. Everything else leads to more confusion than it helps IMO.
Each pipeline shows its description in the overview page, which is stored in the pipeline's DB document. If you press the 'Make new alarm' button it will take the sensor's description by default, but in principle they are independent of each other. (This makes the query easier and was my fix to the flickering)
Pipeline action buttons are now larger for better use on mobile devices.
In the sensor detail modal, we added the possibility to start and stop pipelines directly (no silence button here - should it?).
You can now change the name of a pipeline in the jsoneditor without creating a new pipeline.
Most fields are now uneditable in the jsoneditor since they should never be edited.
Answering question 4. of #16 : you can't create pipelines without prefix alarm_, control_, or convert_ . You will get an error message. This is intentional.
This PR adresses issues #26 #19 and #16 - as far as I agree with it. In detail:
Answering question 4. of #16 : you can't create pipelines without prefix
alarm_,control_, orconvert_. You will get an error message. This is intentional.