定制 digicomp/flowobjectresolving 二次开发

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

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

digicomp/flowobjectresolving

Composer 安装命令:

composer require digicomp/flowobjectresolving

包简介

Helper trait offering an easy and standard way to resolve service classes with nice names

README 文档

README

Build status

This package is here to help your DI to resolve nice human readable names to class names, to the class names which, should be used.

Additionally, it allows you to get a list of all those nice names, so you could list them from a CommandController, if you want to.

class DefaultResolver
{
    use ResolverTrait;

    protected static function getManagedInterface(): string
    {
        return RequestPatternInterface::class;
    }

    protected static function getManagedNamespace(string $packageKey): string
    {
        return 'Security\\RequestPattern\\';
    }
}

This class would for example list the following with a simple getAvailableNames:

['Neos.Flow:ControllerObjectName', 'Neos.Flow:CsrfProtection', 'Neos.Flow:Host',
 'Neos.Flow:Ip', 'Neos.Flow:Uri']

And those plugins can now be resolved to instances with (new DefaultResolver)->resolveObjectName('Neos.Flow:ControllerObjectName') for example. getDefaultNamespace and getDefaultPackage are optional for your resolver and will be resolved to the class, which used the trait, if not overridden.

The ObjectManagerInterface in getDefaultPackageKey is there, because this function makes use of the CompileStatic feature of flow.

The name is build in the scheme: {packageKey}{namespace}{name} - if you need to have different namespaces for different packages, you should implement your conditions, or even use configuration in getManagedNamespace - you'll get the packageKey as argument.

Classes which do not follow the default pattern can still be used, and will be listed, with the FQCN.

digicomp/flowobjectresolving 适用场景与选型建议

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

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

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

围绕 digicomp/flowobjectresolving 我们能提供哪些服务?
定制开发 / 二次开发

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

BUG 修复 & 性能优化

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

项目外包 & 长期维护

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

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

统计信息

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

GitHub 信息

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

其他信息

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