承接 jivochat/entity-exists-constraint 相关项目开发

从需求分析到上线部署,全程专人跟进,保证项目质量与交付效率

邮箱:yvsm@zunyunkeji.com | QQ:316430983 | 微信:yvsm316

jivochat/entity-exists-constraint

Composer 安装命令:

composer require jivochat/entity-exists-constraint

包简介

Symfony validator for checking if Entity Exist

README 文档

README

Software License

This validator verifies that an Entity actually exists in a database. You can use it in different DTO objects. For instance in request object or service dto's

namespace App\Requests;

use JivoChat\Validator\Constraint\EntityExists;
use Symfony\Component\Validator\Constraints as Assert;

final class RequestDto
{
    /**
     * @Assert\NotBlank
     * @EntityExists(entity="Entity\User")
     *
     * @var int User's id property
     * In this case validator will found User primary key. If key has the same name as the parameter (userId), 
     * validator will try to found record in database (where userId = $userId). 
     * If primary key has different name, exception will be thrown
     */
    private $userId;

    /**
     * @Assert\NotBlank
     * @EntityExists(entity="Entity\Post", mapping={"postId": "messageId"}, exception=true)
     *
     * @var int
     * Let's assume that Post has composite primary key userId, postId. Because of the mapping, the validator knows that
     * it must take the value from $messageId and set it to the postId parameter in the query.
     * For the userId parameter it will try to find parameter with the same name or with name from mapping 
     * in the dto object. If parameter will be found, validator will take value. if not, exception will be thrown.

     * Parameter "exception" tells what to do if entity was not found. If it is true, exception will be thrown
     */
    private $messageId;

     /**
     * @Assert\NotBlank
     * @EntityExists(entity="Entity\Transaction", mapping={"ownerId": "userId"}, persistentManager="global")
     *
     * @var int
     * Let's assume that Transaction has primary key transactionId. In this case mapping says to add parameter ownerId 
     * in query and take value from dto parameter $userId (where transactionId = $transactionId AND ownerId = $userId)
     * 
     * Parameter "persistentManager" tells which entity manager using in this case. By default using manager which 
     * contains entity or default manager.
     */
    private $transactionId;

    public  function getUserId(): int
    {
        return $this->userId;
    }

    public  function getMessageId(): int
    {
        return $this->messageId;
    }

    public  function getTransactionId(): int
    {
        return $this->transactionId;
    }
}

You can use default EntityExists constrain from package or make your own to change default parameters.

class EntityExists extends Constraint
{
    /** @var string */
    public $message = 'Entity "%entity%" with parameter "%value%" does not exist.';
    // Violation message. You can use parameters %entity%, %value%, %parameters%

    /** @var string */
    public $entity = '';

    /** @var array<string, string> */
    public $mapping = [];

    /** @var null|string */
    public $persistentManager = null;

    /** @var bool */
    public $exception = false;
    // If it is true, exception will be thrown. It is good then you want to show 404 page

    public function throwException(): void
    {
        throw NotFound::entity($this->entity);
    }
}

Full example

 $dto = new RequestDto();
 $dto->setUserId($request->request->get('user_id'));
 $dto->setMessageId($request->request->get('message_id'));
 $dto->setTransactionId($request->request->get('transaction_id'));

 $violationList = $this->validator->validate($requestDto);
 if ($violationList->count()) {
    ...
 }

Install

composer require jivochat/entity-exists-constraint

Then register the services with:

services:
  JivoChat\Validator\Constraint\EntityExistsValidator:
      arguments: [ '@doctrine' ]
      tags: [ 'validator.constraint_validator' ]

jivochat/entity-exists-constraint 适用场景与选型建议

jivochat/entity-exists-constraint 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 7 次下载、GitHub Stars 达 3, 最近一次更新时间为 2020 年 10 月 18 日, 在 PHP 生态内属于活跃度较高的组件。

我们在过去多个企业项目中使用过 jivochat/entity-exists-constraint 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。

围绕 jivochat/entity-exists-constraint 我们能提供哪些服务?
定制开发 / 二次开发

基于 jivochat/entity-exists-constraint 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。

BUG 修复 & 性能优化

线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。

项目外包 & 长期维护

承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。

yvsm@zunyunkeji.com QQ:316430983 微信:yvsm316 西安尊云信息科技 · 专注 PHP / Go / 分布式系统研发

统计信息

  • 总下载量: 7
  • 月度下载量: 0
  • 日度下载量: 0
  • 收藏数: 3
  • 点击次数: 3
  • 依赖项目数: 0
  • 推荐数: 0

GitHub 信息

  • Stars: 3
  • Watchers: 2
  • Forks: 0
  • 开发语言: PHP

其他信息

  • 授权协议: MIT
  • 更新时间: 2020-10-18