Reintroduced backend webservice monitoring in 369728b using node-fetch.
Fixed #34 using the backend webservice monitoring
Fixed #60 by first checking if the web service port provided in the settings is actually available:
This was preventing backend monitoring to run, as the pipeline instance managed by the application stops immediately with exit code 0 if the assigned port is not available.
In that case, a warning is raised to inform the user that the application will auto-detect a port to be used by the pipeline engine.
Added a validateProps method for the pipeline management class to check if all required props are set and to raise exceptions if not.
Added the web service port information in the tray.
Fixed a possible memory leak on the front end store:
listeners on the pipeline state were rebound on every refresh / re-render of the store component.
The binding is moved to a useEffect to avoid this rebound on refresh.
validatePropsmethod for the pipeline management class to check if all required props are set and to raise exceptions if not.useEffectto avoid this rebound on refresh.