aboutsummaryrefslogtreecommitdiffstats
path: root/activesupport/lib/active_support/deprecation
Commit message (Collapse)AuthorAgeFilesLines
* Fix bug where custom deprecators are not used.Brandon Dunne2015-10-141-12/+36
| | | | | | | | | | | | Add tests for ActiveSupport::Deprecation.deprecate_methods Modify ActiveSupport::Testing::Deprecation to allow a custom deprecator Leverage ActiveSupport::Testing::Deprecation assert_deprecated Update documentation for ActiveSupport::Deprecation.deprecate_methods Use cases: Using the default deprecator => "removed from Rails X.Y" Passing a custom deprecator in the options hash => "removed from MyGem next-release" Deprecating methods directly from custom deprecator => "removed from MyGem next-release"
* Only prepend a single module when defining deprecation wrappers.Charles Oliver Nutter2015-10-131-4/+4
| | | | | I could not find any reason why each method got its own prepended module here, and all tests appear to pass with my change.
* Documentation typoAkira Matsuda2015-09-201-1/+1
| | | | [ci skip]
* use `caller_locations` instead of `caller`Aaron Patterson2015-08-242-3/+14
| | | | | We have `caller_locations`, so we don't need to parse the strings in the callstack.
* A few documentation tweaks [ci skip]Robin Dupret2015-06-072-4/+4
| | | | [Robin Dupret & Shunsuke Aida]
* Merge pull request #20286 from davydovanton/doc-deprecation-behaviorAbdelkader Boudih2015-05-251-0/+12
|\ | | | | Add documentation for Deprecation::Behavior module
| * [skip ci] Add documentation for Deprecation::Behavior moduleAnton Davydov2015-05-251-0/+12
| |
* | s/contstant/constant re #20282 [ci skip]Zachary Scott2015-05-241-2/+2
| |
* | [skip ci] Add documentation for DeprecatedConstantProxy#classAnton Davydov2015-05-241-0/+5
|/
* Tiny documentation edits [ci skip]Robin Dupret2015-05-041-14/+16
| | | | | | * Fix a few typos * Wrap lines to 80 chars * Use `+` instead of `<tt>`
* [ci skip] Rework docs, add examples on deprecation proxiesNick Cox2015-04-241-22/+38
|
* Deprecate alias_method_chain in favour of Module#prependKir Shatrov2015-03-221-3/+5
| | | …as discussed #19413
* Do not check only for the Rails constantRafael Mendonça França2015-01-021-1/+1
| | | | | This constant may be define for auxiliar gems like rails-html-sanitizer and these methods call will fail.
* renames the :abort deprecation behaviour to :raiseXavier Noria2013-08-131-2/+2
| | | | That is a better name, thanks @jeremy.
* defines a new :abort deprecation behaviour that raisesXavier Noria2013-08-131-5/+18
| | | | See the CHANGELONG message in the patch for further details.
* Fix typos in deprecation proxy docs [ci skip]Carlos Antonio da Silva2013-04-301-3/+3
|
* Update activesupport/lib/active_support/deprecation/proxy_wrappers.rbClaudio B.2012-12-071-1/+1
| | | Fix a typo in rdoc (*expect* for *except*)
* nodoc AS::Deprecation::InstanceDelegator class [ci skip]Francesco Rodriguez2012-11-291-3/+3
|
* Make caller attribute in deprecation methods optionalAlexey Gaziev2012-10-302-3/+6
|
* Merge branch 'master' of github.com:lifo/docrailsVijay Dev2012-09-212-8/+8
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: actionmailer/lib/action_mailer/base.rb activesupport/lib/active_support/configurable.rb activesupport/lib/active_support/core_ext/module/deprecation.rb guides/source/action_controller_overview.md guides/source/active_support_core_extensions.md guides/source/ajax_on_rails.textile guides/source/association_basics.textile guides/source/upgrading_ruby_on_rails.md While resolving conflicts, I have chosen to ignore changes done in docrails at some places - these will be most likely 1.9 hash syntax changes.
| * update AS/deprecation docs [ci skip]Francesco Rodriguez2012-09-142-9/+9
| |
* | warning removed: shadowing outer local variable - messageArun Agrawal2012-09-141-2/+2
| |
* | Copy-edit deprecation relared documentation [ci skip]Rafael Mendonça França2012-09-132-22/+24
| |
* | Change ActiveSupport::Deprecation to class.Piotr Niełacny2012-09-135-155/+232
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ActiveSupport::Deprecation is now a class rather than a module. You can get instance of ActiveSupport::Deprecation calling #instance method. ActiveSupport::Deprecation.instance But when you need to get new object od ActiveSupport::Deprecation you need to just call #new. @instance = ActiveSupport::Deprecation.new Since you can create a new object, you can change the version and the name of the library where the deprecator concerned. ActiveSupport::Deprecation.new('2.0', 'MyGem') If you need use another deprecator instance you can select it in the options of deprecate method. deprecate :method, :deprecator => deprecator_instance Documentation has been updated.
* | extend ActiveSupport::Deprecation with self, allow other objects to ↵Robert Pankowecki2012-09-134-101/+104
|/ | | | | | | | | | extend/include it also. test local deprecation deprecator object Test ActiveSupport::Deprecation when included
* fixes a few mistakes in api docs [ci skip]Vijay Dev2012-06-221-1/+1
|
* add example to AS::Deprecation#deprecate_methods [ci skip]Francesco Rodriguez2012-06-181-0/+20
|
* add example to AS::Deprecation#silence [ci skip]Francesco Rodriguez2012-06-171-1/+10
|
* fix bad formatting [ci skip]Vijay Dev2012-05-171-2/+2
|
* copy edit AS deprecation/behaviours docs [ci skip]Vijay Dev2012-05-011-22/+11
|
* Merge branch 'master' of github.com:lifo/docrailsVijay Dev2012-05-011-1/+19
|\
| * Document ActiveSupport::Deprecations.behaviortwinturbo2012-04-291-1/+19
| |
* | Document #behavior= and update CHANGELOGtwinturbo2012-04-281-0/+7
| |
* | Add a "silence" behavior to completely turn off deprecation warnings.Adam Hawkins2012-04-281-2/+3
|/
* revises requires of some AS deprecation filesXavier Noria2012-04-051-2/+2
|
* Remove not used require from as to avoid circular requiresCarlos Antonio da Silva2012-04-051-1/+0
|
* Remove Array.wrap calls in ActiveSupportRafael Mendonça França2012-01-061-2/+1
|
* using the active support loggerKarunakar (Ruby)2012-01-041-2/+2
|
* Changed a few instances of of words in the API docs written in British ↵Oemuer Oezkir2011-07-241-2/+2
| | | | | | English to American English(according to Weber)
* minor changesVijay Dev2011-04-271-3/+1
|
* fixing whitespace errorsAaron Patterson2011-01-121-1/+1
|
* In AS, only inflector/methods is need in proxy_wrappers.rb, as well as date, ↵Josh Kalderimis2011-01-121-1/+1
| | | | | | date_time, and time conversions.rb. This fixes an issue when requiring json and AS saying that i18n is also required. Signed-off-by: Santiago Pastorino <santiago@wyeworks.com>
* Improve documentation on ActiveSupport::Deprecation.Ryan Bigg2010-12-212-1/+14
|
* Prevent any warnings from being printed during RDoc generationJoost Baaij2010-08-261-1/+1
|
* better callstack reporting in deprecation messagesJakub Suder2010-08-251-4/+8
| | | | | | | | | | now the reported line is the first line in the stack that's outside Rails, which is the one that actually caused the problem in the first place [#5231 state:resolved] Signed-off-by: José Valim <jose.valim@gmail.com>
* fixing space errorsAaron Patterson2010-07-261-2/+2
|
* Override new on proxy objects so that they never wrap nil or false.Leigh Caplan2010-07-261-0/+7
|
* fix failure if behavior is not define and try use the defaultCyril Mougel2010-07-011-1/+1
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Add the possibility to have several behaviors in AS::Deprecation.José Valim2010-07-012-3/+5
|
* Create a deprecation behavior that triggers a notification for deprecation ↵wycats2010-06-291-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.