Disclaimer: I'm just describing an annoying technical problem, it's not a blocker for the use of Elm. Elm _is_ great :)
I have been using Elm for a kinda-simple project on my work: dashboard for microservices, deployment configs, nodes, etc.
One of the biggest time-drains was debugging JS-Elm port interactions, looking whether there is a mismatch in types.
Cuz the error looks like this:
Elm eventreceiver failed: Error: Trying to send an
unexpected type of value through port `collectPeerInfo`:
[object Object]
I know of no way of even looking into that `[object Object]`. Simply logging its fields would already be a relief, lest telling what field/type caused the error.
I have been using Elm for a kinda-simple project on my work: dashboard for microservices, deployment configs, nodes, etc.
One of the biggest time-drains was debugging JS-Elm port interactions, looking whether there is a mismatch in types.
Cuz the error looks like this:
I know of no way of even looking into that `[object Object]`. Simply logging its fields would already be a relief, lest telling what field/type caused the error.