rails

History

Vinicius Stock 0966b1983b Turn ActionController::Base inclusions explicit Currently, we are using dynamic inclusions to guarantee that the list of MODULES is always up to date with what gets included into Base. However, that prevents static analysis tools from understanding the ancestors of controllers, which prevents completion and other editor features from working correctly. We can instead use a unit test to verify that both lists are synchronized, which retains the original behavior while allowing for more accurate static analysis.		2024-06-21 21:07:12 +00:00
..
bin	Use frozen string literal in actionpack/	2017-07-29 14:02:40 +03:00
lib	Turn ActionController::Base inclusions explicit	2024-06-21 21:07:12 +00:00
test	Turn ActionController::Base inclusions explicit	2024-06-21 21:07:12 +00:00
actionpack.gemspec	Add allow_browser to set minimum versions for your application (#50505 )	2023-12-31 19:19:16 +01:00
CHANGELOG.md	Keep previous CHANGELOG entry	2024-05-29 22:55:27 +02:00
MIT-LICENSE	Remove Copyright years (#47467 )	2023-02-23 11:38:16 +01:00
Rakefile	Enable Rails minitest plugin in our rake tasks	2024-05-23 16:16:37 +00:00
README.rdoc	🔗 Remove RDoc auto-link from Rails module everywhere	2023-06-23 10:49:30 +09: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. In short, Action Pack
provides the controller layer 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.

You can read more about Action Pack in the {Action Controller Overview}[https://guides.rubyonrails.org/action_controller_overview.html] guide.

== 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/main/actionpack


== License

Action Pack is released under the MIT license:

* https://opensource.org/licenses/MIT


== Support

API documentation is at:

* https://api.rubyonrails.org

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

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

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

* https://discuss.rubyonrails.org/c/rubyonrails-core