def already supports the following form:
def handle_event("event", args, socket) do
# whatever
rescue
e ->
# handle exception here
end
This lets you skip the boilerplate of an additional try do end
benwilson512
Author of Craft GraphQL APIs in Elixir with Absinthe
2
evadne
assuming your LV does crash then on JavaScript side doing this
liveSocket.channel.onError(thing)
should get you a trigger that works
3
soup
Uncaught TypeError: liveSocket.channel.onError is not a function
I don’t think live socket exposes the same interface as the normal socket.
AFAIK, each view has it’s own channel (?), you might be able to hook into each views create/mount call back and use that to bind an “error” handler with the view name (aka channel name?), but I believe the “event” passed around here is more like “phx_update”, not a socket error. I didn’t read too hard or actually test it.
Edit: this.viewName is more like MyApp.View, you need this.__view which is definitely getting weedsy and unsupported, onChannel is marked private too so not recommended to build on.
I think it would be a good feature to have, an easy way to bind per-view error handlers. Maybe another client hook lifecycle callback or a param to destroyed indicating if it was a clean exit or not.
That would probably need the core LV to be patched with the rescue block I guess.
1