This resolves #126 by not attempting to create exception classes. A couple of points no less: 1. The `ActiveRecord` specific exceptions _are_ loaded and merged when its railtie is loaded. Our tests do not load `ActiveRecord` so while they don't exist in our context, they _will_ be around in your garden variety rails application. 2. We essentially replicate what the `ExceptionWrapper` was doing for us, but by leveraging `Rack::Utils.status_code` we avoid the need to create an instance of the actual exception class. Thus avoiding the problems experienced creating exceptions that expect initializer arguments.
Fixes issue #62. This patch allows config.lograge.* to be set effectively in config/initializers/* by delaying the Railtie until after_initialize. Because Railtie initializers run before those app initializers, and the Lograge initializer loads the system only if config.enabled is set at the time it runs, changing config.lograge in config/initializers/* was previously ineffective. A better solution yet would be to always assume enabled=true and let enabling and disabling happen in the Gemfile or app initializers using simply `require 'lograge'`.