You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 7, 2023. It is now read-only.
Currently most exceptions are thrown into one big pile called ArgumentException.
We should specify between derivatives of RuntimeException for input parameters, and specific derivatives of ArgumentException for node errors.
Motivation
You should only handle errors you are able to handle. Therefor you should only catch errors you can process. By having one exception contain all the errors, we are prone to mistakes
The text was updated successfully, but these errors were encountered:
We need to see if we can have Jota throw different exception depending on the cause of the error.
I am especially interested on the case of finding TimeoutExceptions on the server side.
Issue
Currently most exceptions are thrown into one big pile called
ArgumentException
.We should specify between derivatives of
RuntimeException
for input parameters, and specific derivatives ofArgumentException
for node errors.Motivation
You should only handle errors you are able to handle. Therefor you should only catch errors you can process. By having one exception contain all the errors, we are prone to mistakes
The text was updated successfully, but these errors were encountered: