logging-rails
logging-rails copied to clipboard
TwP
Railtie for integrating the Logging framework with Rails
Hi, `ActiveSupport::TaggedLogging` is supposed to be able to wrap ["any standard Logger object"](http://api.rubyonrails.org/v5.1/classes/ActiveSupport/TaggedLogging.html). However, when wrapping an instance of `Logging::Logger`, this does not work: ``` ActiveSupport::TaggedLogging.new(Logging::Logger.new(STDOUT)) => NoMethodError: undefined method...
`config.assets.quiet = true` stopped working when I installed the gem
``` NameError: method `logger' not defined in ActionView::Base [....]/gems/logging-rails-0.6.0/lib/logging/rails/mixin.rb:18:in `remove_method' [....]/gems/logging-rails-0.6.0/lib/logging/rails/mixin.rb:18:in `included' [....]/gems/logging-rails-0.6.0/lib/logging/rails/railtie.rb:35:in `include' ``` 0.5.0 works just fine. More info [here](https://stackoverflow.com/questions/45068612/why-does-ruby-fail-to-remove-method-even-though-it-is-clearly-defined)
I understand the READ access, however, I don't understand why it needs WRITE.
The readme states, this gem is intended for ruby on rails 3, which is outdated at the time of writing this. Is rails 5 support planned?
Gemfile: ``` ruby gem 'logging-rails', require: 'logging/rails' ``` config/loggin.rb The original. config/initializers/logging.rb: ``` ruby Rails.application.configure do if Rails.env.production? config.log_to = %w[file] config.show_log_configuration = false else config.log_to = %w[stdout] config.show_log_configuration =...
By default `Rails.logger` is wrapped. When migrating to logging-rails I usually end up doing this. Any reason not to do this [in the initializer](https://github.com/TwP/logging-rails/blob/logging-rails-0.5.0/lib/logging/rails/railtie.rb#L23)?
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...
``` Logging.backtrace = true # somewhere inside a controller raise StandardError.new("errorz") ``` After some prying, the `format_obj` gets a string representation instead of the raw exception. I assume Rails processes...
