ActionDispatch::Request rather than Rack::Request.

* Changed ActionDispatch::Request#method to return a String, to be
  compatible with the Rack::Request superclass.

* Changed ActionDispatch::Request#method to return the original
  method in the case of methodoverride and #request_method not to,
  to be compatible with Rack::Request

Maintain the usage of :as consistent in the router. Whenever it's supplied, it changes the NAMED ROUTE. If you want to change the PATH, use :path instead. Example: resources :projects, :path => 'projetos'

Mark ActionDispatch::Routing::DeprecatedMapper as nodoc to hide old documentation until it's removed

Signed-off-by: NRizwan Reza <rizwanreza@gmail.com>

Signed-off-by: NRizwan Reza <rizwanreza@gmail.com>

Signed-off-by: Nwycats <wycats@gmail.com>

Signed-off-by: Nwycats <wycats@gmail.com>

Rails router automatically calculated for you the controller and named routes in the following scenarios:

  match "home/about"                 #=> maps to home#about with named route home_about_path
  match "about"                      #=> does not work because it cannot guess the controller
  match "about" => "home#about"      #=> maps to home#about with named route home_about_path
  match "home/about", :as => "about" #=> maps to home#about with named route about_path

globally

Make RouteSet#finalize! a NOOP if it's been called already. Call finalize! the first time call() and url_for() are called if the RouteSet has not been finalized yet.

This reverts commit 5913dd47.

Signed-off-by: NJoshua Peek <josh@joshpeek.com>

Add support for mount RackApp, :at => "/sprockets" with a shorthand of mount Sprockets => "/sprockets". 

This is different from the match syntax in that it cannot be used for controller/action and it does not 
assume an anchor at the end of the match. 

For instance, in the above example, if the client asked for "/sprockets/foo.js", the Sprockets app would
have a SCRIPT_NAME of "/sprockets" and PATH_INFO of "/foo.js".

[#3911 state:committed]
Signed-off-by: NJeremy Kemper <jeremy@bitsweat.net>

add lazy_load_hooks.rb, which allows us to declare code that
should be run at some later time. For instance, this allows
us to defer requiring ActiveRecord::Base at boot time purely
to apply configuration. Instead, we register a hook that should
apply configuration once ActiveRecord::Base is loaded.

With these changes, brings down total boot time of a
new app to 300ms in production and 400ms in dev.

TODO: rename base_hook