We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://github.com/whatyouhide/redix/blob/59224955c788745a2b82b916d19919ec594b53bd/lib/redix/connection.ex#L85C4-L85C21 It would be a better user experience if before exit we had an error or we could return error instead of just exit
The text was updated successfully, but these errors were encountered:
That EXIT is propagating the exit reason of the Redix process and exits the caller process with that reason.
However, yes, we can make it a little bit better. Something like:
exit({:redix_exited_during_call, reason})
Thoughts? I'd appreciate a PR on this, I don't really have any bandwidth right now 🙃
Sorry, something went wrong.
Redix does not provide any error & exit whatyouhide#254
5f1f763
Improve EXITs that happen during calls
d320fa0
Closes #254.
0b5c418
No branches or pull requests
https://github.com/whatyouhide/redix/blob/59224955c788745a2b82b916d19919ec594b53bd/lib/redix/connection.ex#L85C4-L85C21
It would be a better user experience if before exit we had an error or we could return error instead of just exit
The text was updated successfully, but these errors were encountered: