定制 szykra/resource-naming-strategy 二次开发

按需修改功能、优化性能、对接业务系统,提供一站式技术支持

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

szykra/resource-naming-strategy

Composer 安装命令:

composer require szykra/resource-naming-strategy

包简介

Resource Naming Strategy for Doctrine ORM

README 文档

README

building codeclimate version license

Resource Naming Strategy for Doctrine ORM

Why Resource?

This naming strategy following the natural way of thinking about entities and resources. Imagine that you have one Flower. It's single entity. You want to store some data about flowers e.g. in your database. It's resource.

Simple? I know resource named flower sounds easier but sometimes it's more confusing. In the end, you have a lot of flowers, not one.

This strategy is similar to the Laravel naming convention (See mapping section).

Requirements

This package uses icanboogie/inflector and it requires a mbstring php extension.

Instalation

Install via composer

Add dependecy to your composer.json file and run composer update.

"require": {
    "szykra/resource-naming-strategy": "~0.1"
}

Usage

Usage with Doctrine

$namingStrategy = new \Szykra\NamingStrategy\ResourceNamingStrategy();
$configuration()->setNamingStrategy($namingStrategy);

Usage with Symfony

You have a two ways to use this naming strategy

Register bundle in AppKernel.php

Just open your AppKernel.php file and register new symfony bundle which contains a service definition.

$bundles = array(
    ...
    new Szykra\NamingStrategy\ResourceNamingBundle\ResourceNamingBundle()
);

Now you can configure Doctrine in config.yml to use new naming strategy.

doctrine:
    orm:
        naming_strategy: szykra.naming_strategy.resource_naming_strategy

Define your own service

If you don't want to register additional bundles you can create own service definiton in services.yml:

services:
    app.naming_strategy.resource:
        class: Szykra\NamingStrategy\ResourceNamingStrategy

And don't forget to configure Doctrine to use this service.

Mapping

Entity to table name

Lowercase and plural

Entity Table
User users
Category categories
TaskActivity task_activities

Property to column name

Lowercase letters and words separated by the underscore

Property Column
firstName first_name
LastName last_name
secondRememberToken second_remember_token

Embedded field to column name

Lowercase letters and words separated by the underscore

Property from embedded Address Column
street address_street
postcode address_postcode
addressLineOne address_address_line_one

Join column name

Lowercase letters and words separated by the underscore with _id suffix

Property Column
reporter reporter_id
task_activity task_activity_id

Join table name

Two singular lowercase entity names in ascending order with words separated by the underscore

Entity 1 Entity 2 Table
User Task task_user
Comment Post comment_post
Work TimeLog time_log_work

License

The MIT License. Copyright © 2015 - 2020 Szymon Krajewski.

szykra/resource-naming-strategy 适用场景与选型建议

szykra/resource-naming-strategy 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 24.54k 次下载、GitHub Stars 达 4, 最近一次更新时间为 2015 年 04 月 30 日, 在 PHP 生态内属于活跃度较高的组件。

它主要适用于以下技术方向: 「orm」 「symfony」 「doctrine」 「naming」 「resource」 「strategy」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。

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

围绕 szykra/resource-naming-strategy 我们能提供哪些服务?
定制开发 / 二次开发

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

BUG 修复 & 性能优化

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

项目外包 & 长期维护

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

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

统计信息

  • 总下载量: 24.54k
  • 月度下载量: 0
  • 日度下载量: 0
  • 收藏数: 4
  • 点击次数: 29
  • 依赖项目数: 0
  • 推荐数: 0

GitHub 信息

  • Stars: 4
  • Watchers: 2
  • Forks: 1
  • 开发语言: PHP

其他信息

  • 授权协议: MIT
  • 更新时间: 2015-04-30