the 2.0 release of the SVG UI node is almost completed, but would like to have a better error logging mechanism. Currently the errors are written to the console log on the client-side (because most of the stuff happens inside the dashboard), but that is not obvious for users:
- Not all users look in the browser console log.
- When running the dashboard e.g. on an Android smartphone, you have no easy access to e.g. Chrome's console log (unless you setup USB debugging between two Chrome installations ...).
So we would like to get the client-side errors to the node-red flow on the server-side. But don't know how to do this:
- If I'm not mistaken, I can only have a single output port in a UI node (so no second output possible dedicated for error messages). Could send them on the current existing output, but then flows become more complex (to reroute the error messages) and it will break existing flows.
- Suppose I don't want to send error messages on the output, but e.g. call
node.error(...)on the server-side. But when I send as error message from the client to the server, I could intercept that message (to call node.error) but I don't think I can avoid the message from being send on the output. So how should I send then the error info from the client to the server?
Does anybody know a better way to implement this?