Colin Law wrote:
> Do you mean you require that the code runs on the old and new versions
> of rails? Is this always possible?
No. When the Rails maintainers took the default paginator out, and moved it
into
a plugin, they very wisely (not!) decided to upgrade it at the same time. We
have enough mature code, on mature databases with lots of records, that we
needed the old paginator more than we needed to rebuild our views. So I copied
the old paginator out of the old code and crammed it into our lib folder, and
wired up its helpers. It's still online like that...
> In a recent upgrade I had to change
> the base class for my unit tests from Test::Unit::TestCase to
> ActionController::TestCase which I imagine would not have worked had I
> reverted. Are there not other cases of code that cannot be made to work
> in old and new version of rails?
Why didn't you stay with Test::Unit::TestCase? The point of running the tests
was to let them tell you what to upgrade. Because the test.rb file still
mutilates Test::Unit::TestCase directly, we did not need to change it until
after the Final Integration, when we stuck with the higher version number.
> Why does it matter whether the code runs in the old version of rails anyway?
So
all
tests
pass
when
you
integrate!!!
Otherwise you are integrating one huge change, without the ability to safely
revert in small increments.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com
To unsubscribe from this group, send email to
rubyonrails-talk+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
