gears/di 问题修复 & 功能扩展

解决BUG、新增功能、兼容多环境部署,快速响应你的开发需求

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

gears/di

最新稳定版本:v0.2.1

Composer 安装命令:

composer require gears/di

包简介

The gears dependency injection container.

README 文档

README

Build Status Latest Stable Version Total Downloads License

So we have all heard of this thing called Dependency Injection. Its been around for ages in other enterprise enviroments like Java, .Net, etc. But it's sort of new to the PHP world.

Most will understand the general concept but if not check out:

How to Install

Installation via composer is easy:

composer require gears/di:* 

How to Use

Firstly this container is like Pimple but it is not Pimple. There are some unique differences so pay attention.

Basic example:

// lets import the class use Gears\Di\Container;  // create a new container object $container = new Container();  // define some services $container['session_storage'] = function () {  return new SessionStorage('SESSION_ID'); };  $container['session'] = function () {  return new Session($this['session_storage']); };  // get the session object $session = $container['session'];  // define factory service $container['session_factory'] = $container->factory(function() {  return new Session($this['session_storage']); });  // define container parameters / attributes $container['cookie_name'] = 'SESSION_ID';  // protecting parameters $container['random_func'] = $container->protect(function() {  return rand(); });

For someone that has previously used the Pimple container you should note that instead of the container being passed in via a function parameter. It is available via the $this variable. This is because we bind the closure to the container.

Using a Service Provider:

use Gears\Di\Container; use Gears\Di\ServiceProviderInterface;  class FooProvider implements ServiceProviderInterface {  public function register(Container $c)  {  $c['FooService'] = function(){ return new Foo(); };  } }  $container = new Container(); $container->register(new FooProvider()); $container['FooService']->bar();

Object Syntax:

// you can also use the container like this. $container = new Container();  $container->session_storage = function () {  return new SessionStorage('SESSION_ID'); };  $container->session = function () {  return new Session($this->session_storage); };  $session = $container->session;

Extending the Container:

class Mail extends Container {  // note how we prefix the word inject.  // this tells us that the property is injectable  protected $injectTo;   // private properties however will always be  // private and can not be injected directly.  private $sendMailPath;   // so if you tried to inject fooBar it will fail  private $injectFooBar;   // from a naming standpoint I think it is best if you name the injectable  // properties such that it tells you the type that should be injected.  // however this isn't enforced.  protected $injectMessage;   protected $injectTransportService;   // this is where we can define default services for our container.  protected function setDefaults()  {  // notice how we set them without the word inject  $this->to = 'brad@bjc.id.au';   // I could have defined this above directly on the property  // but I would rather keep everything consistent.  $this->sendMailPath = '/bin/sendmail';   $this->message = function()  {  return new Message('Hello World');  };   // take note of the camel case property name vs the definition above.  $this->transportService = function()  {  return new SendMailTransport($this->sendMailPath);  };   // you can use factory and protect too  // note you don't have to explicitly define a class property.  // but just note that both abc and xyz are public properties.  $this->abc = $this->factory(function(){ return new Abc(); });  $this->xyz = $this->protect(function($a,$b){ return $a+$b; });  }   public function send()  {  $this->message->setTo($this->to);  return $this->transportService->send($this->message);  } }  $mail = new Mail(); $mail->send(); // sends an email to me saying Hello World  $mail = new Mail(); $mail->to = 'foo@example.com'; $mail->ip = '127.0.0.1'; $mail->message = function(){ return new Message('bar'); }; $mail->transportService = function(){ return new SmtpTransport($this->ip); }; $mail->send(); // sends an email to foo@example.com via 127.0.0.1 saying bar  // the above could be re written as $mail = new Mail ([  'to' => 'foo@example.com',  'ip' => '127.0.0.1',  'message' => function(){ return new Message('bar'); },  'transportService' => function(){ return new SmtpTransport($this->ip); }, ]); $mail->send();

Credits

This is definitely inspired by Fabien's Pimple Di Container. http://pimple.sensiolabs.org/

Developed by Brad Jones - brad@bjc.id.au

gears/di 适用场景与选型建议

gears/di 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 114.73k 次下载、GitHub Stars 达 1, 最近一次更新时间为 2026 年 01 月 04 日, 在 PHP 生态内属于活跃度较高的组件。

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

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

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

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

BUG 修复 & 性能优化

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

项目外包 & 长期维护

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

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

统计信息

  • 总下载量: 114.73k
  • 月度下载量: 0
  • 日度下载量: 0
  • 收藏数: 1
  • 点击次数: 17
  • 依赖项目数: 13
  • 推荐数: 0

GitHub 信息

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

其他信息

  • 授权协议: MIT
  • 更新时间: 2026-01-04