rails 3 start
I’m starting to play around with Rails 3… perhaps a bit premature, as the beta isn’t even scheduled to release until the end of the month and looking at the open tickets for documentation I’m curious how people are even beginning to plan for code migration.
So I decided yesterday to start looking at the code base. Of course this is really helpful:
http://yehudakatz.com/tags/rails-3/
But I think the most helpful thing really is going to be digging through the framework. Like with the last time I dug into the code, routing seems to be first… maybe because that’s where I expect the most problems to arise in the plugins I’ve developed? Maybe because it seems a logical place to start, being the first entry point at which a request gets processed?
The first problem that I foresee is that I follow a thoughtbot trick to apply Rails Engine routes in an order different from the default. In Rails 2.3, routes added from an engine take precedence over routes in an application. For plugins I want default behavior that can easily be overwritten from within a project (perfect for rapid prototyping where I want to be able to drop in base functionality and overwrite it only where necessary). So far… I’m not seeing an easy parallel.