The Rails core team is cleaning up. That’s obviously a good thing, however it does leave us facing a kabillion deprecation warnings when running tests and whatnot.
Unfortunately the official deprecations page appears to have been thrown together quickly after someone noticed that Rails 1.2 had been pushed out without anyone finishing the page that all deprecation warnings were referring to.
So what does a smart Rails developer who wants to be ready for Rails 2.0 when that time comes around do? She reads on…
| The old, deprecated way | The new, supported way |
|---|---|
|
|
|
|
| The old, deprecated way | The new, supported way |
|---|---|
|
|
| The old, deprecated way | The new, supported way |
|---|---|
|
|
| The old, deprecated way | The new, supported way |
|---|---|
|
|
| The old, deprecated way | The new, supported way |
|---|---|
|
|
| The old, deprecated way | The new, supported way |
|---|---|
|
|
Yeah, I know, thanks for pointing it out, though. The above messages are basically just the ones I have encountered in my projects. I will continue to update this page as I encounter more. Or even better, the Rails team could grab the above HTML and merge it with the stuff already on rubyonrails.org, making for what might just be a usable deprecation page.
Until then, hopefully this page will help out a few people.
There is also this:
http://wiki.rubyonrails.com/rails/pages/Deprecated+Patterns
Thanks for posting the above examples, I’ve been going through my application and trying to update everything.