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
I agree, out the box logging-rails turns on the firehose. It should only add the logger to things that Rails does by default. This does not include Rails.cache and ActiveSupport::Dependencies.logger.
It also (somehow) adds the logger to seemingly random classes at startup.
I like a lot logging and also logging-rails due to that. However, I don't particularly like automagical inclusion of "logger" everywhere via ::Logging::Rails::Mixin done in https://github.com/TwP/logging-rails/blob/master/lib/logging/rails/railtie.rb.
While this is not problem with small project, with larger projects is starts to blur things a bit and creates hidden extra dependency.
So I would see beneficial to have option to turn off auto mixin, and have module, which would explicitly include "logger" method in the context.
For example,
The text was updated successfully, but these errors were encountered: