Pionia 框架是一个 PHP Rest 框架，它正在改变我们过去开发 Rest 平台的方式。与所有现有框架不同，它使整个流程焕然一新，使 API 的开发变得更加简单，不再那么枯燥。这是因为它运行在一种不同的、相当“新”的模式上，称为月光。
月光本身并不是一种新的架构/模式，大多数机构/公司/开发者都在使用它，但只是未命名。不过今天我们不是在谈论月光，你可以在我的另一篇文章中阅读它，甚至留下你的评论。
要引导一个新的 Pionia 项目，假设您已经设置了 Composer，则需要运行以下命令。
让我们创建一个todo_app。
composer create-project pionia/pionia-app todo_app
登录后复制
您还可以使用 pionia 命令运行相同的项目，如下所示：
要实时查看日志，请打开第二个终端并运行以下命令：
服务背景。
Pionia 框架中的服务是核心，可能是您在开发 API 时花费大部分时间的唯一部分。 Pionia 中的所有正常服务都扩展了 PioniaRequestBaseRestService。 Pionia 中的正常服务可能如下所示。
namespace application\services;
use Exception;
use Pionia\Request\BaseRestService;
use Pionia\Response\BaseResponse;
use Porm\Porm;
class UserService extends BaseRestService
{
/**
* @throws Exception
*/
protected function login(array $data): BaseResponse
{
// password and username are required, without them we won't proceed even
$this->requires(["username", "password"]);
$username = $data["username"];
$password = password_hash($data['password'], PASSWORD_DEFAULT);
$user = Porm::from('user')->get(['username' => $username, 'password' => $password]);
//You can do more here, maybe generate a JWT token or add more checks
// for example if the user is an active or not
if ($user) {
return BaseResponse::JsonResponse(0, "Login successful", $user);
}
throw new Exception("User with the given username and password not found");
}
}
登录后复制
构建服务后，您需要在从现在开始处理它的交换机中注册它。如果您不知道 Pionia 中的开关，您可以在文档中阅读有关它们的信息。因此，请转到我们的 Switch 文件夹（如果您尚未创建另一个文件夹，可能位于 MainAppSwitch.php 中），然后在 registerServices 方法中注册上述服务，如下所示
/**
* Register your services here.
*
* @return array
*/
public function registerServices(): array
{
return [
'user' => new UserService(),
'todo' => new TodoService()
];
}
登录后复制
从现在开始，这就是让内核自动发现您的服务的方法。在典型设置中，您将添加一个路由器和一个控制器来映射到此服务，但 Pionia 的处理方式有所不同。请记住，您可以在多个交换机中注册相同的服务。这就是我们实现 API 版本控制概念的方式，因为每个开关都由其 API 端点处理。默认情况下，可以在 /api/v1/ 上访问 MainAppSwitch。
在您的请求中，您可以通过发送以下内容来指向此服务。
// POST http://localhost:8000/api/v1/
{
"SERVICE": "user",
"ACTION": "login",
"username": "pionia",
"password": "pionia1234"
}
登录后复制
如果您注意到，ACTION 是我们在 SERVICE/service/class 中创建的操作/方法的名称，我们在注册时为用户名称命名。
这就是 Pionia 正常服务的运作方式。
下面是在 Piona 中执行 CRUD 的完整服务。它基于名为 todo_db 的 MySQL 数据库中名为 todos 的以下简单表。
create table todo_db.todos
(
id int auto_increment primary key,
title varchar(200) not null,
description text null,
created_at timestamp default CURRENT_TIMESTAMP null
) engine = InnoDB;
登录后复制
use Exception;
use Pionia\Request\BaseRestService;
use Pionia\Request\PaginationCore;
use Pionia\Response\BaseResponse;
use Porm\exceptions\BaseDatabaseException;
use Porm\Porm;
class TodoService extends BaseRestService
{
/**
* Returns all todos
* @throws Exception
*/
public function list(): BaseResponse
{
$result = Porm::table('todos')
->using('db')
->columns(['id', 'title', 'description', 'created_at'])
->all();
return BaseResponse::JsonResponse(0, null, $result);
}
/**
* Returns a single todo
* @throws Exception
*/
public function details(array $data): BaseResponse
{
$this->requires(['id']);
$id = $data['id'];
$result = Porm::table('todos')
->using('db')
->columns(['id', 'title', 'description', 'created_at'])
->get(['id' => $id]);
return BaseResponse::JsonResponse(0, null, $result);
}
/**
* Creates a new todo
* @throws Exception
*/
public function create(array $data): BaseResponse
{
$this->requires(['title', 'description']);
$title = $data['title'];
$description = $data['description'];
$result = Porm::table('todos')
->save(['title' => $title, 'description' => $description]);
return BaseResponse::JsonResponse(0, 'Todo created successfully', $result);
}
/**
* Updates a todo
* @throws Exception
*/
public function update(array $data): BaseResponse
{
$this->requires(['id']);
$id = $data['id'];
$todo = Porm::table('todos')
->get($id); // similar to `get(['id' => $id])`
// if the todo is not found, we throw an exception
if (!$todo) {
throw new BaseDatabaseException('Todo not found');
}
$description = $data['description'] ?? $todo->description;
$title = $data['title'] ?? $todo->title;
// we update in a transaction as below
$result= null;
Porm::table('todos')
->inTransaction(function () use ($description, $title, $id, &$result) {
Porm::table('todos')
->update(['description' => $description, 'title' => $title], $id);
$result = Porm::table('todos')
->get($id);
});
return BaseResponse::JsonResponse(0, "Todo $id updated successfully", $result);
}
/**
* Deletes a todo
* @throws Exception
*/
public function delete(array $data): BaseResponse
{
$this->requires(['id']);
$id = $data['id'];
$todo = Porm::table('todos')
->get($id);
if (!$todo) {
throw new BaseDatabaseException('Todo not found');
}
$deleted = false;
Porm::table('todos')
->inTransaction(function () use ($id, &$deleted) {
Porm::table('todos')
->delete($id);
$deleted = true;
});
if (!$deleted) {
throw new BaseDatabaseException('Todo not deleted');
}
return BaseResponse::JsonResponse(0, "Todo $id deleted successfully");
}
/**
* Returns a random todo object if the size is not defined or 1,
* else returns an array of random todos
* @throws Exception
*/
public function random($data): BaseResponse
{
$size = $data['size'] ?? 1;
$result = Porm::table('todos')
->random($size);
return BaseResponse::JsonResponse(0, null, $result);
}
/**
* Returns a paginated list of todos
* @throws Exception
*/
public function paginatedList(array $data): BaseResponse
{
$offset = $data['offset'] ?? 0;
$limit = $data['limit'] ?? 3;
$paginator = new PaginationCore($data, 'todos', $limit, $offset, 'db');
$result = $paginator->paginate();
return BaseResponse::JsonResponse(0, null, $result);
}
}
登录后复制
由于我们的 TodoService 已经注册，这就是我们需要做的全部，无需添加额外的路由，无需添加控制器，只需开始点击请求中的操作，您应该从所有上述操作中获得统一的响应。
但是这并不是很多事情要做，而且是 Pionia（构建服务）中唯一要做的事情，我们的 TodoService 中的所有上述操作都可以省略，我们仍然获得相同的功能，这就是我们的位置通用服务登场！
Todo 服务，通用方式。
如果您的逻辑不只是创建、删除、分页、列出、更新、删除或检索，那么通用服务可能就是您所需要的。
Pionia 提供通用服务和 mixin 供使用。 Mixins 可以组合在一起来构建整个新的通用服务。
提供的 mixins 包括 ListMixin、CreateMixin、DeleteMixin、UpdateMixin、RandomMixin 和 RetrieveMixin。在底层，即使是通用服务也只是在扩展 GenericService 的同时组合这些 Mixin。
提供的通用服务包括RetrieveCreateUpdateService、RetrieveListCreateService、RetrieveListCreateUpdateDeleteService、RetrieveListDeleteService、RetrieveListRandomService、RetrieveListUpdateDeleteService、RetrieveListUpdateService 和UniversalGenericService。
如果上述泛型没有按照您想要的方式组合 mixin，您可以扩展 GenericService 并调用您想要使用的所有 mixin，从而创建自定义通用服务。
请记住，要使用 mixins，您必须扩展 PioniaGenericsBaseGenericService，而不是我们之前扩展的普通 BaseRestService。另外，请记住 mixin 只是 PHP 特性，应该以这种方式使用。
要重构我们的 TodoService，我们需要最后提到的通用服务 UniversalGenericService，因为它使用所有定义的 mixin。
让我们从更改我们扩展的类开始。重构如下
use Pionia\Generics\UniversalGenericService;
// ... rest of the imports
class TodoService extends UniversalGenericService
{
// ... rest of your actions
}
登录后复制
Before we do anything, let's first define the table we want to target in the database. We use the $table property for this. This is a compulsory feature and must be defined for all generic views.
use Pionia\Generics\UniversalGenericService;
// ... rest of the imports
class TodoService extends UniversalGenericService
{
public string $table = "todo";
// ... rest of your actions
}
登录后复制
Secondly, from our list action, we are defining columns we want to return, however, we are defining all. If you want to return a certain range of columns only, we define the $listColumns(which defaults to all) and pass the columns we want to return. Let's just still pass all though it is the default behavior of the service.
use Pionia\Generics\UniversalGenericService;
// ... rest of the imports
class TodoService extends UniversalGenericService
{
public string $table = "todo";
public ?array $listColumns = ['id', 'title', 'description', 'created_at'];
// ... rest of your actions
}
登录后复制
At this point, we can delete the list action from our service. That's complete!
Our second target action is now details. This one can be replaced by defining the $pk_field which defaults to id. Since our primary key field for our todo table is also id, we don't need to define it, we just need to delete it too! Remember, this one also uses the defined $listColumns for columns to return from the DB.
The RetrieveMixin also defines another sister action to this called retrieve, so in your request, you can use ACTION as details or retrieve, the two will perform the same thing.
Since we already have all we need, we can drop the details action too!
Our third action is create. For this, we must define the $createColumns to define those columns we shall be looking for from the request(required) to create a record. Let's add the property now.
use Pionia\Generics\UniversalGenericService;
// ... rest of the imports
class TodoService extends UniversalGenericService
{
public string $table = "todo";
public ?array $listColumns = ['id', 'title', 'description', 'created_at'];
public ?array $createColumns = ['title', 'description'];
// ... rest of your actions
}
登录后复制
After adding, go ahead and delete it too!
Our fourth action is update. For this, we require the $pk_field and can also optionally define the $updateColumns. If undefined, the responsible mixin checks if any of the properties were defined in the request, and will update only those.
Let's add the $updateColumns and give it the only properties we intend to update.
use Pionia\Generics\UniversalGenericService;
// ... rest of the imports
class TodoService extends UniversalGenericService
{
public string $table = "todo";
public ?array $listColumns = ['id', 'title', 'description', 'created_at'];
public ?array $createColumns = ['title', 'description'];
public ?array $updateColumns = ['title', 'description'];
// ... rest of your actions
}
登录后复制
We can now drop the update action too!
For our fifth action, delete, we only need the $pk_field which is by default id, so we shall be checking if id was passed in the request, and then we delete the associated record. So, just delete it, we already have all we need!
Now to our sixth action, random, this also uses the $listColumns to determine the columns to fetch from the DB per record. We already have out property defined, so, just drop it too!
For our seventh action, paginatedList, we can drop it, and in any request, we target our list action, but we define any of the following pairs of keys in our request.
-
limit and offset on the request object level.
{
"SERVICE": "todo",
"ACTION": "list",
"limit": 3,
"offset": 0
}
登录后复制
-
PAGINATION or pagination object on the request with limit and offset keys.
{
"SERVICE": "todo",
"ACTION": "list",
"PAGINATION": {
"limit": 3,
"offset": 0,
}
}
登录后复制
-
SEARCH or search object on the request object with limit and offset keys.
{
"SERVICE": "todo",
"ACTION": "list",
"SEARCH": {
"limit": 3,
"offset": 0
}
}
登录后复制
Note: Both the limit and offset keys must be defined for pagination to kick in.
And just like that, our service now has been reduced to the following.
use Pionia\Generics\UniversalGenericService;
class TodoService extends UniversalGenericService
{
public string $table = "todo";
public ?array $listColumns = ['id', 'title', 'description', 'created_at'];
public ?array $createColumns = ['title', 'description'];
public ?array $updateColumns = ['title', 'description'];
}
登录后复制
Let's do a little more cleanup. As we had mentioned earlier, if we are listing all columns from our table, then we don't need to define the $listColumns property, let's remove that too.
use Pionia\Generics\UniversalGenericService;
class TodoService extends UniversalGenericService
{
public string $table = "todo";
public ?array $createColumns = ['title', 'description'];
public ?array $updateColumns = ['title', 'description'];
}
登录后复制
Also, since our update can also discover the columns to update from the request data, let's remove the $updateColumns too!
And we are left with the following as our new TodoService but still exposing the actions of list(all and paginated), create, update, delete, retrieve or details and random
use Pionia\Generics\UniversalGenericService;
class TodoService extends UniversalGenericService
{
public string $table = "todo";
public ?array $createColumns = ['title', 'description'];
}
登录后复制
You can also override how we get a single record and multiple records. You might not need it, but sometimes you may need to add where clauses and other conditions as you see fit. For that, you can read about it in this section in the docs.
Also, you may want to add your other actions in the same generic service, this is fully supported and will work as if you're in normal services, however, make sure none of those actions share the names with the provided mixin actions or otherwise you stand a chance of overriding the provided actions.
This also drives to the last point, what if you intend to override the default action? that's also okay! You can also look into it under this section of the docs.
Welcome to Pionia Framework, where we believe in both developer and program performance, writing precise and maintainable codebase with simplicity both at the front end and the back end!
Let me hear what you say about the Pionia Framework specifically about generic services. Happy coding!
以上是Pionia 通用服务终极指南。的详细内容。更多信息请关注PHP中文网其他相关文章！
