Frederick Cheung wrote:
It was deprecated in 1.2 and removed in 2.0
On the subject of error messages, with deprecations specifically in
mind, I suggest the following approach at least be considered.
Establish a deprecated_methods_index library at the top level of Rails
so that, when someone finally decides to upgrade their Rails-1.0.6 app
to Rails-whatever, instead of getting:
"undefined local variable or method `whatever'"
(which is generated by ruby itself and not by Rails)
one obtains the output from something like this:
puts("whatever method is deprecated and was removed in rails-x.y.z.")
puts("Use other_one method instead.")
If these are all kept in one place surely it would not be too difficult
to maintain? Are there any downsides to this approach, other than having
to write four lines of code for every deprecated method?