Download the PHP package eboreum/caster without Composer
On this page you can find all versions of the php package eboreum/caster. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download eboreum/caster
More information about eboreum/caster
Files in eboreum/caster
Package caster
Short Description Cast any PHP value to a sensible, human readable string. Great for type-safe outputs, exception messages, transparency during debugging, and similar things. Also helps avoiding innate problems such as printing endless, circular referencing objects (endless recursion), limits the output for large arrays and long strings, and prevents (opt-in) the outputting of sensitive strings like passwords.
License MIT
Informations about the package caster
Eboreum/Caster: A PHP type formatter
Cast any PHP value to a sensible, human readable string. Great for type-safe outputs, exception messages, transparency during debugging, and similar things. Also helps avoiding innate problems such as printing endless, circular referencing objects (endless recursion), limits the output for large arrays and long strings, and prevents (opt-in) the outputting of sensitive strings like passwords.
Why use Eboreum/Caster instead things like XDebug, symfony/var-dumper
, and similar libraries?
XDebug, symfony/var-dumper
, and similar libraries are meant for development environments.
Eboreum/Caster is meant for any and all environments (development, test, staging, production).
With Eboreum/Caster, you will be able to provide excellent information about all PHP values, which is great in both debugging and failure scenarios. Are the exception messages in your application lacklustre? Expand your options and displayed values greatly with Eboreum/Caster!
This package can be thought of as an extended version of the magic method __debugInfo
(https://www.php.net/manual/en/language.oop5.magic.php#object.debuginfo). However, contrary to __debugInfo
, where only the internals of the implementing class is used for building sensible debug information – with the occasional (often abominable) static method calls to other classes – Caster allows for much more variety, including custom formatters utilizing proper dependency injection.
Eboreum/Caster gives you -- the developer -- the ultimate power to control how output is handled, parsed and presented through opt-in utilization of custom formatters.
Lastly, you may provide a series of sensitive text strings like passwords, authentication tokens, social security numbers, and similar, preventing these from being output inside strings. Wouldn't want these to show up in error logs, emails, and what have you. Upon encountering sensitive strings, said sensitive substrings will be masked, instead showing a static length string replacement (like ******
).
Requirements
For more information, see the composer.json
file.
Installation
Via Composer (https://packagist.org/packages/eboreum/caster):
composer install eboreum/caster
Via GitHub:
git clone [email protected]:eboreum/caster.git
Fundamentals
Type conversions to string
The data types are converted as illustrated in the table below.
Type | Conversion logic | Example(s) | Note |
---|---|---|---|
Null | As is. | null |
|
Booleans | As is. | true false |
|
Float numbers | As is. | 3.14 |
Standard float-to-string conversion rounding will occur, as produced by strval(3.14) . |
Integers | As is. | 42 |
|
Strings | As is or as a sample (substring). | "foo" "bar ..." (sample) |
If you wish to control how strings are presented or apply conditions, you may do so by providing an instance of \Eboreum\Caster\Contract\Formatter\StringFormatterInterface . More on this interface and implementation further down. |
Arrays | As is or as a sample. | [0 => "foo"] [0 => "bar" ... and 9 more elements] |
Sub-arrays By default, no sub-arrays are displayed; i.e. the depth is zero. However, a custom depth may be specified. Sub-arrays with depth 0 (zero) may appear as such: [0 => (array(1)) [...]] Sub-arrays with depth 1 may appear as such: [0 => (array(1)) ["foo"]] Sampling and sample size By default, a maximum of 3 elements are displayed, before the " ... and X more elements" message is displayed. This number is also customizible. Custom array-to-string conversion If you wish to customize how arrays are being converted to a string, you may do so by providing an instance of \Eboreum\Caster\Contract\Formatter\ArrayFormatterInterface . More on this interface and implementation further down. |
Objects | Class namespace with leading backslash. | \stdClass class@anonymous/in/foo/bar/baz.php:22 |
Objects are rather complex types. As such, something sensible besides its class name cannot be reliably displayed. Not even using __toString or similar methods.Custom object-to-string conversion If you wish to customize how objects are being converted to a string, you may do so by providing an instance of \Eboreum\Caster\Contract\Formatter\ObjectFormatterInterface . More on this interface and implementation Doctrine ORM entities. |
Resource_ | A text and the resource's ID. | #Resource id #2 |
Resources can be many different things. A file pointer, database connection, image canvas, etc. As such, only the bare minimum of information is displayed. Custom resource-to-string conversion If you wish to customize how resources are being converted to a string, you may do so by providing an instance of \Eboreum\Caster\Contract\Formatter\ResourceFormatterInterface . More on this interface and implementation further down. |
Output examples
Echo
Example:
Output:
Exception
Example:
Output:
Usage
\Eboreum\Caster\Caster
is immutable. This is a great guard against tampering with the internals of the Caster class. However, a multitude of with*
methods are supplied, allowing clones to be mutated.
It is recommended that you, in your own application, implement a \My\Application\Caster
, which extends \Eboreum\Caster\Caster
and overrides the getInstance
method, from where you may gain full control over your own application's instance of the caster.
Example:
Output:
The standard formatter
By default, Eboreum\Caster\Caster::create()
returns a new instance every time. If you wish to re-use the same instance over and over, you have two options.
Option 1: Store it in a variable and use that. As such:
Option 2: Use getInstance
.
For ease-of-use, you may retrieve the same instance by calling \Eboreum\Caster\Caster::getInstance()
. As describe above, it is recommended you make you own \My\Application\Caster::getInstance()
in your application or library.
Use a real Dependency Injection Container
Alternatively, use an actual Dependency Injection Container (DIC) such as Pimple. However, this means you will have to pass around the dependencies everywhere you need them, which - from a SOLID perspective - is nice, but not always very practical.
A custom basic formatter
You may customize the formatter to your specific needs, e.g. changing string sample size, array depth, or providing custom array and/or object formatters.
Example:
Output:
Type specific formatters
The following type specific formatters exist, which may help providing additional information. Especially useful for printing relevant information relating to an object.
Add formatters (immutably) to the \Eboreum\Caster\Caster
using the with*
methods (returns a clone).
Data type | \Eboreum\Caster\Caster method |
Interface | Note |
---|---|---|---|
array |
withCustomArrayFormatterCollection |
\Eboreum\Caster\Contract\Formatter\ArrayFormatterInterface |
See usage example in Custom array formatter further down. |
object |
withCustomObjectFormatterCollection |
\Eboreum\Caster\Contract\Formatter\ObjectFormatterInterface |
See usage example in below. |
resource |
withCustomResourceFormatterCollection |
\Eboreum\Caster\Contract\Formatter\ResourceFormatterInterface |
See usage example in Custom resource formatter further down. |
string |
withCustomStringFormatterCollection |
\Eboreum\Caster\Contract\Formatter\StringFormatterInterface |
See usage example in Custom string formatter further down. |
Multiple custom formatters can be provided, such that they each handle only specific cases. Order is significant. The first element in the collection is handled first. You must order the collection elements, before passing them to \Eboreum\Caster\Caster
.
Ultimately, all custom formatters fall back to their respective standard formatters.
Included object formatters
The following object formatters are readily available. You may use them as-is or extend them, providing your own custom logic. Everything is very Open-closed Principle.
Namespace: \Eboreum\Caster\Formatter\Object_
Class name | Description | Output example(s) |
---|---|---|
DateIntervalFormatter |
Formats \DateInterval objects. |
\DateInterval {$y = 0, $m = 1, $d = 2, $h = 12, $i = 34, $s = 56, $f = 0, $weekday = 0, $weekday_behavior = 0, $first_last_day_of = 0, $invert = 0, $days = 33, $special_type = 0, $special_amount = 0, $have_weekday_relative = 0, $have_special_relative = 0} |
DatePeriodFormatter |
Formats \DatePeriod objects. |
\DatePeriod (start: \DateTimeImmutable ("2020-01-01T00:00:00+00:00"), end: \DateTimeImmutable ("2020-01-01T00:00:00+00:00"), recurrences: null, interval: \DateInterval) |
DateTimeInterfaceFormatter |
Formats \DateTimeInterface objects, appending ISO 8601 time in parenthesis. |
\DateTimeImmutable ("2019-01-01T00:00:00+00:00") |
DebugIdentifierAttributeInterfaceFormatter |
Formats objects, which implement the interface \Eboreum\Caster\Contract\DebugIdentifierAttributeInterface . |
class@anonymous/in/foo/bar/baz.php:22 {$foo = 42} ($path = "/foo.php") |
DirectoryFormatter |
Formats \Directory objects, as produced by dir(__DIR__) . |
\Directory ($path = "/foo.php") |
PublicVariableFormatter |
Formats any object which has publicly accessible variables. | \stdClass {$foo = "bar"} |
SplFileInfoFormater |
Formats \SplFileInfo objects. |
\SplFileInfo ("/my/system/foo.txt") |
TextuallyIdentifiableInterfaceFormatter |
Formats objects, which implement the interface \Eboreum\Caster\Contract\TextuallyIdentifiableInterface . |
\MyUserClass (USER.ID = 22) |
ThrowableFormatter |
Formats instances of \Throwable .Caution: The output is greatly simplified compared to properly dumping a \Throwable with stack trace and everything else. |
\RuntimeException {$code = 0, $file = "/foo.php", $line = 22, $message = "bar", $previous = null} |
Custom array formatter
Example:
Output:
Custom object formatter
In this example, \DateTimeInterface
and \Throwable
are utilized to supply good real-world use cases.
Example:
Output:
Custom resource formatter
Example:
Output:
Custom string formatter
Example:
Output:
Hiding sensitive substrings
You may hide sensitive strings such as passwords, authentication tokens, social security numbers, and similar.
In the example below, notice how "345" and "456" overlap, causing the product of these strings, "3456", to be masked. While this can potentially reveal, that one sensitive string is part of another, it is a lesser evil compared to masking out only one of them, and then revealing the remainder of the second sensitive string in the plain text output.
Will mask out in the order: Longest sensitive string to shortest. Meaning, with sensitive strings "foo"
and "foobar"
, "foobar"
is handled first. This string, "foobarbaz"
, will become "******baz"
, and "foo"
in this case is never handled. The string "foob foobarbaz"
will become "******b ******baz"
, and so on.
The sensitive strings are encrypted (IV and salt are randomized at runtime), such that if Eboreum/Caster should fail internally, it will not reveal the sensitive strings in clear text.
When using \Eboreum\Caster\Caster->cast(...)
, any string is masked before it is passed on to a string formatter (a class implementing StringFormatterInterface
).
Example:
Output:
Tests
Test/development requirements
Running tests
For all unit tests, first follow these steps:
PHPStan
Suppression codes
For a few cases, we need to suppress the PHPStan output, for various reasons. We strive to avoid @phpstan-ignore-line
(and @phpstan-ignore-next-line
, and similar), but in very few cases – primarily in tests – this is just not possible, as the very thing we test for is something PHPStan does not like.
Code | Remark |
---|---|
babdc1d2 | A property is never read, only written. See: https://phpstan.org/developing-extensions/always-read-written-properties. For tests, where the existence of such properties is integral to the tests, PHPStan shouldn't show it as an error. Sometimes, it is because a property is read through the Reflection API and not directly accessed, which confuses PHPStan. |
136348fe | False positive by PHPStan on the error: "Dead catch - Exception is never thrown in the try block." |
03dec37a | On-purpose testing for an invalid argument in a test, which is the very test, and as such, PHPStan should not report on it. |
License & Disclaimer
See LICENSE
file. Basically: Use this library at your own risk.
Contributing
We prefer that you create a ticket and or a pull request at https://github.com/eboreum/caster, and have a discussion about a feature or bug here.
Please do not require https://packagist.org/packages/eboreum/exceptional back into this project. We do not want a bidirectional dependency as eboreum/exceptional utilizes eboreum/caster.
Credits
Authors
- Kasper Søfren (kafoso)
E-mail: https://github.com/kafoso - Carsten Jørgensen (corex)
E-mail: https://github.com/corex
Acknowledgements
Originates from and replaces: https://packagist.org/packages/kafoso/type-formatter (https://github.com/kafoso/type-formatter).
All versions of caster with dependencies
ext-mbstring Version *
ext-openssl Version *