-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error handling strategy #4
Comments
Good idea. I'll look into it. |
Do you mean on the front end or the back? On the front end there is an optional "error-fn" That can be provided to the "websocket-chan" and "request" functions that gets called on error |
Backend. |
Ah -- it would definitely be nice to have middleware on the backend, for instance having some logging and authentication layers seem like near-term needs. Especially if we can manage a "session" associated with each peer. |
It would be neat if when exposing an api with think.peer, the user could provide a function to be called in case of errors (middleware-esque)
The text was updated successfully, but these errors were encountered: