roave/strict-php
Composer 安装命令:
composer require roave/strict-php
包简介
A strict runtime type and invariant checker for developing safer PHP applications
README 文档
README
StrictPhp is a development tool aimed at bringing stricter runtime assertions into PHP applications and libraries.
Authors
Installation
$ composer require roave/strict-php
Please note that the current version has unstable dependencies.
In order to install those dependencies, you can set "minimum-stability" in
your composer.json:
{
"minimum-stability": "dev"
}
Usage
After installing StrictPhp, point it at the directory to be checked at runtime
(the code that you are writing) via following code:
\StrictPhp\StrictPhpKernel::bootstrap([ 'debug' => true, // change this if you use this tool on multiple projects: 'cacheDir' => sys_get_temp_dir(), 'includePaths' => [ __DIR__ . '/path/to/your/sources', ], ]);
StrictPhp will then intercept any runtime operations that are considered "illegal" and throw an exception or a catchable fatal error.
Please remember to execute this code before any code that may autoload any of the classes that should be checked.
Configuration
The StrictPhp\StrictPhpKernel can be initialized with a set of options to be passed
to go-aop-php and a set of feature
flags:
StrictPhp\StrictPhpKernel::CHECK_STATE_AFTER_CONSTRUCTOR_CALLStrictPhp\StrictPhpKernel::JAIL_PUBLIC_METHOD_PARAMETERSStrictPhp\StrictPhpKernel::CHECK_STATE_AFTER_PUBLIC_METHOD_CALLStrictPhp\StrictPhpKernel::CHECK_PUBLIC_METHOD_PARAMETER_TYPEStrictPhp\StrictPhpKernel::CHECK_PUBLIC_METHOD_RETURN_TYPEStrictPhp\StrictPhpKernel::CHECK_PROPERTY_WRITE_IMMUTABILITYStrictPhp\StrictPhpKernel::CHECK_PROPERTY_WRITE_TYPE
Each of these features are described below.
Features
StrictPhp currently supports following features:
Per-property type checks
Enabled via flag StrictPhp\StrictPhpKernel::CHECK_PROPERTY_WRITE_TYPE.
This feature will prevent your application from assigning illegal values to properties that are type-hinted (via docblock) differently. As an example, consider following class:
class Example { /** * @var int|null */ public $integer; }
Following code will work:
$object = new Example(); $object->integer = 123;
Following code will crash:
$object = new Example(); $object->integer = '123';
Please note that this kind of feature currently only works with public and protected properties.
Return type checks
Quite similar to the above functionality, this feature will prevent your application from returning illegal values from methods that are type-hinted (via docblock) differently. As an example, consider following method:
class Example { /** * @return string */ public function dummyReturn($value) { return $value; } }
Following code will work:
(new Example())->dummyReturn('string');
Following code will crash:
(new Example())->dummyReturn(123);
Please note that this kind of feature currently only works with public and protected methods.
immutable properties
Enabled via flag StrictPhp\StrictPhpKernel::CHECK_PROPERTY_WRITE_IMMUTABILITY.
This feature will prevent your application from overwriting object properties
that are marked as @immutable. As an example, consider following class:
class Example { /** * @immutable */ public $immutableProperty; }
Following code will crash:
$object = new Example(); $object->immutableProperty = 'a value'; echo 'Works till here!'; $object->immutableProperty = 'another value'; // crash
Please note that this kind of feature currently only works with public and protected properties.
Public constructor property initialization checks
Enabled via flag StrictPhp\StrictPhpKernel::CHECK_STATE_AFTER_CONSTRUCTOR_CALL.
This feature of StrictPhp allows checking whether a public constructor of a class fully initialized an object.
Following code will make StrictPhp crash your application:
class Example { /** * @var array */ private $arrayProperty; public function __construct() { } }
In order to make this code work, you have to either annotate $arrayProperty
with @var array|null, or make the constructor initialize the property
correctly:
class Example { /** * @var array */ private $arrayProperty; public function __construct() { $this->arrayProperty = ['initial status']; } }
Parameter interface jailing
Enabled via flag StrictPhp\StrictPhpKernel::JAIL_PUBLIC_METHOD_PARAMETERS.
This feature of StrictPhp "jails" (restricts) calls to non-interfaced methods whenever an interface is used as a type-hint.
Following example will work, but will crash if StrictPhp is enabled:
interface HornInterface { public function honk(); } class TheUsualHorn implements HornInterface { public function honk() { var_dump('honk'); } public function sadTrombone() { var_dump('pooapooapooapoaaaa'); } } class Car { public function honk(HornInterface $horn, $sad = false) { if ($sad) { // method not covered by interface: crash $horn->sadTrombone(); return; } // interface respected $horn->honk(); } }
$car = new Car(); $horn = new TheUsualHorn(); $car->honk($horn, false); // works $car->honk($horn, true); // crashes
This prevents consumers of your APIs to design their code against non-API methods.
Parameter checking
Enabled via flag StrictPhp\StrictPhpKernel::CHECK_PUBLIC_METHOD_PARAMETER_TYPE.
StrictPhp also provides a way to check parameters types in more detail during public method calls.
Specifically, the following code will work in PHP:
final class Invoice { /** * @param LineItem[] $lineItems */ public function __construct(array $lineItems) { // ... } } $invoice = new Invoice(['foo', 'bar']);
This code will crash in StrictPhp due to the type mismatch in $lineItems (which
should be a collection of LineItem objects instead).
Current limitations
This package uses voodoo magic to operate, specifically go-aop-php.
Go AOP PHP has some limitations when it comes to intercepting access to private class members, so please be aware that it has limited scope (for now).
This package only works against autoloaded classes; classes that aren't handled by an autoloader cannot be rectified by StrictPhp.
License
This package is released under the MIT license.
Contributing
If you wish to contribute to the project, please read the CONTRIBUTING notes.
roave/strict-php 适用场景与选型建议
roave/strict-php 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 128 次下载、GitHub Stars 达 261, 最近一次更新时间为 2015 年 06 月 26 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「php」 「development」 「continuous integration」 「analysis」 「strict」 「type safety」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 roave/strict-php 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 roave/strict-php 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 roave/strict-php 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
Debugging a problem and need to login as one of your customers? This allows you to authenticate as any of your customers.
Lot's of tools for git, file and static source code analysis.
Library with classes to help you do batch.
Feature Flip, Feature Flag, Feature Switch
GHT D-Tools Bundle
Migration style post deployment commands for Laravel
统计信息
- 总下载量: 128
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 262
- 点击次数: 22
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2015-06-26