There are a few places in @jdaigneau's API wrapper where a catch block throws the exception it catches. The technical term for this is wack. You should either: 1. not catch the exception (and allow the calling functions to catch them) 2. handle the exception gracefully (this could mean notifying the user about what went wrong, logging events, restarting a service, etc.)
There are a few places in @jdaigneau's API wrapper where a catch block throws the exception it catches. The technical term for this is wack.
You should either: