Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Improve documentation on ActiveSupport::Deprecation. | Ryan Bigg | 2010-12-21 | 1 | -0/+7 |
| | |||||
* | fix failure if behavior is not define and try use the default | Cyril Mougel | 2010-07-01 | 1 | -1/+1 |
| | | | | Signed-off-by: José Valim <jose.valim@gmail.com> | ||||
* | Add the possibility to have several behaviors in AS::Deprecation. | José Valim | 2010-07-01 | 1 | -1/+2 |
| | |||||
* | Create a deprecation behavior that triggers a notification for deprecation ↵ | wycats | 2010-06-29 | 1 | -9/+12 |
| | | | | | | | | | | | | | | | | | notices, and make the behaviors independent of the environment names. * In Rails 2.3 apps being upgraded, you will need to add the deprecation configuration to each of your environments. Failing to do so will result in the same behavior as Rails 2.3, but with an outputted warning to provide information on how to set up the setting. * New Rails 3 applications generate the setting * The notification style will send deprecation notices using ActiveSupport::Notifications. Third-party tools can listen in to these notifications to provide a streamlined view of the deprecation notices occurring in your app. * The payload in the notification is the deprecation warning itself as well as the callstack from the point that triggered the notification. | ||||
* | Add subscriber for ActionPack and move all logging inside it. | José Valim | 2010-01-13 | 1 | -1/+1 |
| | |||||
* | Explicitly require logger | Jeremy Kemper | 2009-10-14 | 1 | -1/+7 |
| | |||||
* | Make logger work again (h/t Sam Ruby) | Yehuda Katz | 2009-10-13 | 1 | -1/+1 |
| | |||||
* | Dice up ActiveSupport::Deprecation | Jeremy Kemper | 2009-04-17 | 1 | -0/+32 |