29 docs tagged with "component"

Actions serve as the embodiment of the application's Use Cases,

Apiato provides a Role-Based Access Control (RBAC) through its Authorization Container.

Apiato commands are just Laravel Commands,

In the Container layer of Porto,

Apiato configs are just Laravel configs, and they function in the exact same way as Laravel configs.

Controllers are tasked with two primary responsibilities:

To prevent overlap with the L5 Repository documentation, this page

Apiato events are just Laravel Events,

Exceptions are used to handle errors and exceptions in the application.

Apiato factories are just Laravel Factories,

You have the option to create your own global "helper" PHP functions in designated directories, and Apiato will automatically autoload them for you.

Apiato jobs are just Laravel Jobs,

Apiato mails are just Laravel Mails,

Apiato middlewares are just Laravel Middlewares,

Apiato migrations are just Laravel Migrations,

Models are responsible for representing the data of the application

Apiato notifications are just Laravel Notifications,

Apiato policies are just Laravel Policies,

Apiato provides a powerful repository pattern implementation based on the L5 Repository package.

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.

Apiato seeders are just Laravel Seeders,

Apiato service providers are just Laravel Service Providers,

SubActions are designed to eliminate code duplication within Actions.

Tasks are specialized classes that hold shared business logic,

Apiato is built with testing in mind.

Transformers,

Value Objects are short names for known "Value Objects",

Views offer a convenient mechanism for organizing HTML content in separate files.