This is part 3 of a series taking an in-depth look at how the internals of Rails handle requests and produce responses - be sure to catch up on previous parts!
Last time we focused on how requests are routed to controller actions through Journey and the ActionDispatch stack. This time, we'll look at ActionController and how controller actions turn into a rendered view.
The last post ended with the
#dispatch method of the
ActionDispatch::RouteSet::Dispatcher, which actually calls the controller action. Here's that method as recap: