wickedbyte / http-tortilla
Set of traits that make wrapping PSR-7 objects easier.
Requires
- php: ~8.2.0 || ~8.3.0 || ~8.4.0 || ~8.5.0
- psr/http-message: ^1.1 || ^2.0
Requires (Dev)
- jangregor/phpstan-prophecy: ^2.2.0
- php-parallel-lint/php-parallel-lint: ^1.4
- phpspec/prophecy-phpunit: ^2.4
- phpstan/extension-installer: ^1.4
- phpstan/phpstan: ^2.1
- phpstan/phpstan-phpunit: ^2.0
- phpunit/phpunit: ^11.5 || ^12.0
- rector/rector: ^2.1
- wickedbyte/coding-standard: ^1.0
This package is auto-updated.
Last update: 2026-03-20 02:17:29 UTC
README
This project is an independently maintained fork of phoneburner/http-tortilla, originally released under the MIT license, by the original project authors. This fork is neither affiliated with nor endorsed by PhoneBurner.
This library provides a simple set of traits to allow wrapping (or decoration) of various PSR-7 classes. Wrapping the classes allows easy addition of convenience methods while maintaining compatibility with code that relies on the underlying PSR interfaces.
Requirements
- PHP >= 8.2
psr/http-message^1.1 || ^2.0
This package works with either v1.1 or v2.0 of the PSR-7 interfaces, but does not provide the actual implementations to
be wrapped. Those can be found in other packages, e.g. guzzlehttp/psr-7 or
Laminas Diactoros.
Installation
The preferred method of installation is to use Composer:
composer require wickedbyte/http-tortilla
Usage
To add behaviour to a PSR-7 object that implements MessageInterface or one of its subclasses, use the matching
wrapper trait, and call setMessage($message) to wrap the target object.
Once setMessage($message) is called, all interface methods will be proxied to the original object. Any of those methods
can be redefined, however, most usage will probably be adding additional convenience methods to the object.
Because most with*() methods will likely evolve the wrapped object as the method is proxied to that underlying
object. To maintain the wrapping through various calls to with*(), setFactory($callable) allows a callable that
returns a wrapped object when given the product of the underlying with*() message.
If the underlying object needs to be accessed, getMessage() may be used.
<?php declare(strict_types=1); use Psr\Http\Message\ServerRequestInterface; use WickedByte\Http\Message\ServerRequestWrapper; class Request implements ServerRequestInterface { use ServerRequestWrapper; public function __construct(ServerRequestInterface $request) { // wrap this object, and proxy all the interface methods to it $this->setMessage($request); // wrap all proxied `with*` methods in this function $this->setFactory(function(ServerRequestInterface $request){ // now `with*` will return an instance of the current class return new self($request); }); } }
Examples
Perhaps it would be convenient to access query parameters as a collection (and not the interface's array):
<?php declare(strict_types=1); use Psr\Http\Message\ServerRequestInterface; use WickedByte\Http\Message\ServerRequestWrapper; class Request implements ServerRequestInterface { use ServerRequestWrapper; public function __construct(ServerRequestInterface $request) { $this->setMessage($request); $this->setFactory(fn(ServerRequestInterface $request) => new self($request)); } public function getQueryCollection() { return new Collection($this->getQueryParams()); } }
Or perhaps the underlying library doesn't handle parsing JSON requests:
<?php declare(strict_types=1); use Psr\Http\Message\ServerRequestInterface; use WickedByte\Http\Message\ServerRequestWrapper; class Request implements ServerRequestInterface { use ServerRequestWrapper; public function __construct(ServerRequestInterface $request) { $this->setMessage($request); $this->setFactory(fn(ServerRequestInterface $request) => new self($request)); } public function getParsedBody() { if ($parsed = $this->getMessage()->getParsedBody()) { return $parsed; } $decoded = json_decode($this->getBody(), true); if (json_last_error() == JSON_ERROR_NONE) { return $decoded; } return $parsed; } }
Contributing
Contributions are welcome, please see CONTRIBUTING.md for more information, including reporting bugs and creating pull requests.
Coordinated Disclosure
Keeping user information safe and secure is a top priority, and we welcome the contribution of external security researchers. If you believe you've found a security issue, please read SECURITY.md for instructions on submitting a vulnerability report.