{"action":"created","issue":{"url":"https://api.github.com/repos/TwP/logging-rails/issues/10","labels_url":"https://api.github.com/repos/TwP/logging-rails/issues/10/labels{/name}","comments_url":"https://api.github.com/repos/TwP/logging-rails/issues/10/comments","events_url":"https://api.github.com/repos/TwP/logging-rails/issues/10/events","html_url":"https://github.com/TwP/logging-rails/issues/10","id":8823392,"number":10,"title":"breaks ActiveSupport::OrderedOptions","user":{"login":"igorbernstein","id":71188,"avatar_url":"https://avatars.githubusercontent.com/u/71188?v=3","gravatar_id":"","url":"https://api.github.com/users/igorbernstein","html_url":"https://github.com/igorbernstein","followers_url":"https://api.github.com/users/igorbernstein/followers","following_url":"https://api.github.com/users/igorbernstein/following{/other_user}","gists_url":"https://api.github.com/users/igorbernstein/gists{/gist_id}","starred_url":"https://api.github.com/users/igorbernstein/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/igorbernstein/subscriptions","organizations_url":"https://api.github.com/users/igorbernstein/orgs","repos_url":"https://api.github.com/users/igorbernstein/repos","events_url":"https://api.github.com/users/igorbernstein/events{/privacy}","received_events_url":"https://api.github.com/users/igorbernstein/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2012-11-29T18:42:06Z","updated_at":"2015-03-29T17:39:18Z","closed_at":null,"body":"ActiveSupport::OrderedOptions relies on ```method_missing``` to configure a rails application.  By default logging-rails monkey patches Object to ```include Logging.globally```.  This makes it impossible to configure loggers:\n\n```\nRails.configuration.assets.logger = Logging::Logger[Sprockets]\nputs Rails.configuration.assets.logger.name # ActiveSupport::OrderedOptions\n\n``````\n\nMy current workaround is:\n```\nActiveSupport::OrderedOptions.send :undef_method, :logger\n```"},"comment":{"url":"https://api.github.com/repos/TwP/logging-rails/issues/comments/87449743","html_url":"https://github.com/TwP/logging-rails/issues/10#issuecomment-87449743","issue_url":"https://api.github.com/repos/TwP/logging-rails/issues/10","id":87449743,"user":{"login":"gingerlime","id":524274,"avatar_url":"https://avatars.githubusercontent.com/u/524274?v=3","gravatar_id":"","url":"https://api.github.com/users/gingerlime","html_url":"https://github.com/gingerlime","followers_url":"https://api.github.com/users/gingerlime/followers","following_url":"https://api.github.com/users/gingerlime/following{/other_user}","gists_url":"https://api.github.com/users/gingerlime/gists{/gist_id}","starred_url":"https://api.github.com/users/gingerlime/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gingerlime/subscriptions","organizations_url":"https://api.github.com/users/gingerlime/orgs","repos_url":"https://api.github.com/users/gingerlime/repos","events_url":"https://api.github.com/users/gingerlime/events{/privacy}","received_events_url":"https://api.github.com/users/gingerlime/received_events","type":"User","site_admin":false},"created_at":"2015-03-29T17:39:18Z","updated_at":"2015-03-29T17:39:18Z","body":"Hi @igorbernstein, I'm sorry but I'm not sure I follow you completely.\r\n\r\nAre you saying that `logging-rails` should continue to monkey-patch Object, so all objects have access to `logger` or that it shouldn't do it?\r\n\r\nI know that monkey-patching is generally fraught with danger, and should be avoided. Particularly when it comes to monkey-patching things like Object. But is there another / better way to allow all modules and classes in my rails app to have access to `logger` and maintain the context info of where the logging took place in the code?"}}