This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
commit fcce1f17eaf9993b0210fe8e2a8117b61a1f0f69
tree dcf89fab841f873dd9c26b3f061f7d1c4e378f86
parent 4b33fae1f52325d22083de2e83d827b924d1c616
tree dcf89fab841f873dd9c26b3f061f7d1c4e378f86
parent 4b33fae1f52325d22083de2e83d827b924d1c616
- actionpack/lib/action_controller/dispatcher.rb
- activesupport/lib/active_support/dependencies.rb
- railties/CHANGELOG
- railties/Rakefile
- railties/doc/guides/source/layouts_and_rendering.txt
- railties/helpers/application.rb
- railties/helpers/application_controller.rb
- railties/lib/rails_generator/generators/applications/app/app_generator.rb
... |
... |
|
... |
... |
|
... |
... |
|
... |
... |
|
... |
... |
|
... |
... |
|












Saw that coming ;)
Makes sense for 3.0, not sure about 2.3 though.
Maybe still load application.rb if it exists and spit out a deprecation notice? That way there can be a transitioning version.
I remember way back when…”ApplicationController” was just called “Application.”
Those were the days.
+1 ryanb
great!
yay!
This should be a 3.0 change, imo.
+1 ryanb phase this change in gradually =)
Finally!
that makes more sense.
+1 for ryanb. Any big api change should at lease get some deprecation warning and isn’t this a little much for a minor release.
We haven’t really decided if 2.2.next will be 2.3 or 3.0. Also, ‘rake rails:update’ task should/will take care of renaming application.rb -> application_controller.rb.
Isn’t 2.3 going to be released as 3.0? I thought that is how it worked. 1.2.x lead to 2.0.x … so 2.2.x will give way to 3.0.x!
Regardless, keep up the good work!
I remember when this was being discussed. Glad to see it finally making its way into core!
I don’t see this being a problem as a 2.3 release – it’s a single file name change, it’s not as if there’s a change to a major API function.
When this gets pushed into a release we’ll naturally take care to make the upgrade path as smooth as possible.
However, if you’re tracking edge right now, just after a branch, you’re braver than I am :)
At last!
1+ for ranaming
Anyone else getting an ActionController::MethodNotAllowed when visiting / since this?
nm its unrelated, seems map.root is generating me a POST rather than a GET route :S
I still think a transitioning version (where application.rb is loaded and deprecated) would be nice. Not for development (it’s easy enough to rename a file), but for deployment in production. Now you’ll have to push this change to the server the exact same time you upgrade Rails. Having a stepping-stone version where both application.rb and application_controller.rb work would ease this transition.
After thinking about it a bit more I suppose it’s not as big of an issue. It’s easy enough to make a second branch, change the gem version in the config, fix all the problems, and then deploy that all to the server in one go.
@ryanb: 2.2.something could end up being the transitioning version you’re talking about, or we could add the deprecation / warnings into master.
Again, this isn’t how we’re going to ship anything, and chasing edge is risky, especially this soon after a branch where we have a bunch of features / patches we pushed out as ‘too risky’.
@topfunky: oh yeah, well I remember abstract_application_controller.rb. Take that!
abstract_application_controller.rb! whoa
My only problem with calling it application_controller is that it indicates that it is a controller in MVC, which it isn’t. It has features that all other controllers share.
@evilgeenius the class has been called ApplicationController for quite some time. This patch just makes the file name consistent with the class name. Consistency is a good thing.
huzzah!
@ryanb i concede
With this commit you’ll need to update your phusion passenger—but it might be better to hack the solution yourself than try to be fancy and update the gem.
See my note in comments at http://ryandaigle.com/articles/2008/11/19/what-s-new-in-edge-rails-application-rb-duality-is-no-more