rails

History

Rafael Sales 4db921a8e7 Allow multiple `root` routes in same scope level When an application has multiple root entries with different constraints, the current solution is to use `get '/'`. Example: Currently I have to do: ```ruby get '/', to: 'portfolio#show', constraints: ->(req) { Hostname.portfolio_site?(req.host) } get '/', to: 'blog#show', constraints: ->(req) { Hostname.blog_site?(req.host) } root 'landing#show' ``` But I would like to do: ```ruby root 'portfolio#show', constraints: ->(req) { Hostname.portfolio_site?(req.host) } root 'blog#show', constraints: ->(req) { Hostname.blog_site?(req.host) } root 'landing#show' ``` Other URL matchers such as `get`, `post`, etc, already allows this, so I think it's fair that `root` also allow it since it's just a shortcut for a `get` internally.		2015-10-10 08:22:31 -03:00
..
bin	select the AR adapter through `bin/test`.	2015-06-11 14:24:56 +02:00
lib	Allow multiple `root` routes in same scope level	2015-10-10 08:22:31 -03:00
test	Use `Mime[:foo]` instead of `Mime::Type[:FOO]` for back compat	2015-10-06 11:29:30 -07:00
actionpack.gemspec	point at rack master	2015-08-20 13:45:11 -07:00
CHANGELOG.md	Allow multiple `root` routes in same scope level	2015-10-10 08:22:31 -03:00
MIT-LICENSE	Update copyright notices to 2015 [ci skip]	2014-12-31 08:34:14 +01:00
Rakefile	Remove unused package tasks	2015-05-28 09:06:10 +02:00
README.rdoc	[ci skip] Don’t encourage `sudo gem install`	2015-05-12 14:51:19 -07:00

README.rdoc

= Action Pack -- From request to response

Action Pack is a framework for handling and responding to web requests. It
provides mechanisms for *routing* (mapping request URLs to actions), defining
*controllers* that implement actions, and generating responses by rendering
*views*, which are templates of various formats. In short, Action Pack
provides the view and controller layers in the MVC paradigm.

It consists of several modules:

* Action Dispatch, which parses information about the web request, handles
  routing as defined by the user, and does advanced processing related to HTTP
  such as MIME-type negotiation, decoding parameters in POST, PATCH, or PUT bodies,
  handling HTTP caching logic, cookies and sessions.

* Action Controller, which provides a base controller class that can be
  subclassed to implement filters and actions to handle requests. The result
  of an action is typically content generated from views.

With the Ruby on Rails framework, users only directly interface with the
Action Controller module. Necessary Action Dispatch functionality is activated
by default and Action View rendering is implicitly triggered by Action
Controller. However, these modules are designed to function on their own and
can be used outside of Rails.


== Download and installation

The latest version of Action Pack can be installed with RubyGems:

  % gem install actionpack

Source code can be downloaded as part of the Rails project on GitHub

* https://github.com/rails/rails/tree/master/actionpack


== License

Action Pack is released under the MIT license:

* http://www.opensource.org/licenses/MIT


== Support

API documentation is at

* http://api.rubyonrails.org

Bug reports can be filed for the Ruby on Rails project here:

* https://github.com/rails/rails/issues

Feature requests should be discussed on the rails-core mailing list here:

* https://groups.google.com/forum/?fromgroups#!forum/rubyonrails-core