Action subclasses are simply wrappers to allow a large method to be refactored into multiple smaller methods.
Controller subclasses contain methods, conventionally called actions and called such within documentation.
This is confusing from a developer standpoint, if someone mentions an "action", are they talking about an Action? Or a controller action?
Action
subclasses are simply wrappers to allow a large method to be refactored into multiple smaller methods.Controller
subclasses contain methods, conventionally calledactions
and called such within documentation.This is confusing from a developer standpoint, if someone mentions an "action", are they talking about an
Action
? Or a controller action?