Actions
Actions serve as the embodiment of the application's Use Cases,
Actions serve as the embodiment of the application's Use Cases,
Controllers are tasked with two primary responsibilities:
Exceptions are used to handle errors and exceptions in the application.
Models are responsible for representing the data of the application
Requests components are a way to interact with the current HTTP request
Routes are responsible for mapping incoming HTTP requests to their corresponding controller functions.
SubActions are designed to eliminate code duplication within Actions.
Tasks are specialized classes that hold shared business logic,
Transformers,
Views offer a convenient mechanism for organizing HTML content in separate files.