When EAAL gets an error from the EVE API (not a transport error, mind - a proper error code from the EVE API), it automatically spawns a class called EveAPIExceptionXXX, where XXX is a numeric code from the API.
This is extremely undesirable for two reasons:
- I can't handle specific errors since their exception class isn't defined until the exception actually occurs. I want to handle a small subset (relating to bad API keys) differently from the rest (and mark the keys as proved-invalid).
- There isn't a clean way to log the numeric code -- you either get the whole class name, or do some string mogging on
#class.to_s.
The exceptions caused by transport issues suffer a similar problem w.r.t the error codes.
When EAAL gets an error from the EVE API (not a transport error, mind - a proper error code from the EVE API), it automatically spawns a class called
EveAPIExceptionXXX, where XXX is a numeric code from the API.This is extremely undesirable for two reasons:
#class.to_s.The exceptions caused by transport issues suffer a similar problem w.r.t the error codes.