Top Related Projects
Thin assertion library for use in libraries and business-model
The PHP Unit Testing framework.
Data transfer objects with batteries included
🔰 Instant PHP quality checks from your console
Quick Overview
Webmozarts/assert is a PHP library that provides a collection of assertion functions for input validation. It offers a simple and expressive way to validate method input/output and other values in your PHP applications, helping to catch and prevent errors early in the development process.
Pros
- Easy to use and integrate into existing PHP projects
- Provides a wide range of assertion functions for various data types
- Throws meaningful exceptions with clear error messages
- Helps improve code quality and reduce bugs
Cons
- May introduce a slight performance overhead in some cases
- Requires developers to be familiar with assertion concepts
- Could lead to overly defensive programming if overused
Code Examples
- Basic string assertion:
use Webmozart\Assert\Assert;
Assert::string($value, 'The value must be a string.');
- Asserting array keys:
use Webmozart\Assert\Assert;
Assert::keyExists($array, 'key', 'The array must contain the key "key".');
- Validating email addresses:
use Webmozart\Assert\Assert;
Assert::email($email, 'Invalid email address provided.');
- Checking numeric ranges:
use Webmozart\Assert\Assert;
Assert::range($number, 0, 100, 'The number must be between 0 and 100.');
Getting Started
To use Webmozarts/assert in your PHP project, follow these steps:
- Install the library using Composer:
composer require webmozart/assert
- Include the Composer autoloader in your PHP file:
require_once 'vendor/autoload.php';
- Use the assertion functions in your code:
use Webmozart\Assert\Assert;
function processUser(array $userData)
{
Assert::keyExists($userData, 'name', 'User data must contain a name.');
Assert::string($userData['name'], 'User name must be a string.');
Assert::notEmpty($userData['name'], 'User name cannot be empty.');
// Process user data...
}
Competitor Comparisons
Thin assertion library for use in libraries and business-model
Pros of Assert (beberlei)
- More extensive set of assertion methods, offering a wider range of validation options
- Supports chaining of assertions for more concise and readable code
- Includes specialized assertions for common data types like arrays, objects, and strings
Cons of Assert (beberlei)
- Larger library size, which may impact performance in some scenarios
- Less frequent updates and maintenance compared to Assert (webmozart)
- Slightly more complex API, which might have a steeper learning curve for beginners
Code Comparison
Assert (beberlei):
Assert::that($value)
->notEmpty()
->string()
->startsWith('foo')
->endsWith('bar');
Assert (webmozart):
Assert::notEmpty($value);
Assert::string($value);
Assert::startsWith($value, 'foo');
Assert::endsWith($value, 'bar');
Both libraries provide similar functionality, but Assert (beberlei) allows for method chaining, while Assert (webmozart) uses separate method calls for each assertion. The beberlei version may be more concise in some cases, but the webmozart version can be more explicit and easier to read for complex assertions.
The PHP Unit Testing framework.
Pros of PHPUnit
- Comprehensive testing framework with a wide range of features
- Extensive documentation and large community support
- Integrates well with various IDEs and CI/CD tools
Cons of PHPUnit
- Steeper learning curve for beginners
- Heavier and more complex setup compared to lightweight assertion libraries
- May be overkill for small projects or simple assertion needs
Code Comparison
Assert:
use Webmozart\Assert\Assert;
Assert::string($value);
Assert::allString($array);
Assert::keyExists($array, 'key');
PHPUnit:
use PHPUnit\Framework\TestCase;
class ExampleTest extends TestCase
{
public function testAssertions()
{
$this->assertIsString($value);
$this->assertContainsOnly('string', $array);
$this->assertArrayHasKey('key', $array);
}
}
Assert is a lightweight library focused solely on assertions, making it easy to use and integrate into existing projects. It provides a clean API for common assertion types.
PHPUnit, on the other hand, is a full-featured testing framework that includes assertions along with test organization, mocking, and reporting capabilities. It's more suitable for comprehensive testing suites but requires more setup and knowledge to use effectively.
Data transfer objects with batteries included
Pros of data-transfer-object
- Provides a structured way to define and validate data objects
- Offers type-hinting and auto-completion for object properties
- Supports nested objects and collections
Cons of data-transfer-object
- More complex setup and usage compared to simple assertions
- Requires creating separate classes for each data structure
- May introduce additional overhead for simpler data validation scenarios
Code Comparison
assert:
use Webmozart\Assert\Assert;
Assert::string($value);
Assert::length($value, 5);
data-transfer-object:
use Spatie\DataTransferObject\DataTransferObject;
class UserData extends DataTransferObject
{
public string $name;
public int $age;
}
Key Differences
- assert focuses on individual value assertions, while data-transfer-object provides a complete object structure
- data-transfer-object offers stronger typing and object-oriented approach
- assert is more lightweight and easier to integrate for simple validations
Use Cases
- Use assert for quick, inline validations and simple data checks
- Choose data-transfer-object for complex data structures, API responses, and when working with larger datasets
Community and Maintenance
Both projects are actively maintained and have good community support. assert has a larger user base due to its simplicity and broader use cases, while data-transfer-object caters to more specific object-oriented validation needs.
🔰 Instant PHP quality checks from your console
Pros of PHPInsights
- Provides comprehensive code quality analysis and metrics
- Offers a user-friendly CLI interface with detailed reports
- Integrates multiple tools (PHP_CodeSniffer, PHPCPD, PHPMD) into a single package
Cons of PHPInsights
- Heavier and more complex than Assert, which focuses solely on assertions
- May require more configuration and setup time
- Can be overkill for projects that only need simple assertion functionality
Code Comparison
Assert:
use Webmozart\Assert\Assert;
Assert::string($value);
Assert::allString($array);
Assert::nullOrString($value);
PHPInsights:
use NunoMaduro\PhpInsights\InsightsApplication;
$application = new InsightsApplication();
$result = $application->run();
echo $result->getCodeQuality();
Summary
Assert is a lightweight library focused on providing robust assertion functions, while PHPInsights is a comprehensive code quality analysis tool. Assert is ideal for simple validation tasks, whereas PHPInsights offers in-depth analysis and reporting for larger projects. The choice between the two depends on the specific needs of your project and the level of code quality analysis required.
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual CopilotREADME
Webmozart Assert
This library contains efficient assertions to test the input and output of your methods. With these assertions, you can greatly reduce the amount of coding needed to write a safe implementation.
All assertions in the Assert
class throw an Webmozart\Assert\InvalidArgumentException
if
they fail.
FAQ
What's the difference to beberlei/assert?
This library is heavily inspired by Benjamin Eberlei's wonderful assert package, but fixes a usability issue with error messages that can't be fixed there without breaking backwards compatibility.
This package features usable error messages by default. However, you can also easily write custom error messages:
Assert::string($path, 'The path is expected to be a string. Got: %s');
In beberlei/assert, the ordering of the %s
placeholders is different for
every assertion. This package, on the contrary, provides consistent placeholder
ordering for all assertions:
%s
: The tested value as string, e.g."/foo/bar"
.%2$s
,%3$s
, ...: Additional assertion-specific values, e.g. the minimum/maximum length, allowed values, etc.
Check the source code of the assertions to find out details about the additional available placeholders.
Installation
Use Composer to install the package:
composer require webmozart/assert
Example
use Webmozart\Assert\Assert;
class Employee
{
public function __construct($id)
{
Assert::integer($id, 'The employee ID must be an integer. Got: %s');
Assert::greaterThan($id, 0, 'The employee ID must be a positive integer. Got: %s');
}
}
If you create an employee with an invalid ID, an exception is thrown:
new Employee('foobar');
// => Webmozart\Assert\InvalidArgumentException:
// The employee ID must be an integer. Got: string
new Employee(-10);
// => Webmozart\Assert\InvalidArgumentException:
// The employee ID must be a positive integer. Got: -10
Assertions
The Assert
class provides the following assertions:
Type Assertions
Method | Description |
---|---|
string($value, $message = '') | Check that a value is a string |
stringNotEmpty($value, $message = '') | Check that a value is a non-empty string |
integer($value, $message = '') | Check that a value is an integer |
integerish($value, $message = '') | Check that a value casts to an integer |
positiveInteger($value, $message = '') | Check that a value is a positive (non-zero) integer |
float($value, $message = '') | Check that a value is a float |
numeric($value, $message = '') | Check that a value is numeric |
natural($value, $message= ''') | Check that a value is a non-negative integer |
boolean($value, $message = '') | Check that a value is a boolean |
scalar($value, $message = '') | Check that a value is a scalar |
object($value, $message = '') | Check that a value is an object |
resource($value, $type = null, $message = '') | Check that a value is a resource |
isCallable($value, $message = '') | Check that a value is a callable |
isArray($value, $message = '') | Check that a value is an array |
isTraversable($value, $message = '') (deprecated) | Check that a value is an array or a \Traversable |
isIterable($value, $message = '') | Check that a value is an array or a \Traversable |
isCountable($value, $message = '') | Check that a value is an array or a \Countable |
isInstanceOf($value, $class, $message = '') | Check that a value is an instanceof a class |
isInstanceOfAny($value, array $classes, $message = '') | Check that a value is an instanceof at least one class on the array of classes |
notInstanceOf($value, $class, $message = '') | Check that a value is not an instanceof a class |
isAOf($value, $class, $message = '') | Check that a value is of the class or has one of its parents |
isAnyOf($value, array $classes, $message = '') | Check that a value is of at least one of the classes or has one of its parents |
isNotA($value, $class, $message = '') | Check that a value is not of the class or has not one of its parents |
isArrayAccessible($value, $message = '') | Check that a value can be accessed as an array |
uniqueValues($values, $message = '') | Check that the given array contains unique values |
Comparison Assertions
Method | Description |
---|---|
true($value, $message = '') | Check that a value is true |
false($value, $message = '') | Check that a value is false |
notFalse($value, $message = '') | Check that a value is not false |
null($value, $message = '') | Check that a value is null |
notNull($value, $message = '') | Check that a value is not null |
isEmpty($value, $message = '') | Check that a value is empty() |
notEmpty($value, $message = '') | Check that a value is not empty() |
eq($value, $value2, $message = '') | Check that a value equals another (== ) |
notEq($value, $value2, $message = '') | Check that a value does not equal another (!= ) |
same($value, $value2, $message = '') | Check that a value is identical to another (=== ) |
notSame($value, $value2, $message = '') | Check that a value is not identical to another (!== ) |
greaterThan($value, $value2, $message = '') | Check that a value is greater than another |
greaterThanEq($value, $value2, $message = '') | Check that a value is greater than or equal to another |
lessThan($value, $value2, $message = '') | Check that a value is less than another |
lessThanEq($value, $value2, $message = '') | Check that a value is less than or equal to another |
range($value, $min, $max, $message = '') | Check that a value is within a range |
inArray($value, array $values, $message = '') | Check that a value is one of a list of values |
oneOf($value, array $values, $message = '') | Check that a value is one of a list of values (alias of inArray ) |
String Assertions
You should check that a value is a string with Assert::string()
before making
any of the following assertions.
Method | Description |
---|---|
contains($value, $subString, $message = '') | Check that a string contains a substring |
notContains($value, $subString, $message = '') | Check that a string does not contain a substring |
startsWith($value, $prefix, $message = '') | Check that a string has a prefix |
notStartsWith($value, $prefix, $message = '') | Check that a string does not have a prefix |
startsWithLetter($value, $message = '') | Check that a string starts with a letter |
endsWith($value, $suffix, $message = '') | Check that a string has a suffix |
notEndsWith($value, $suffix, $message = '') | Check that a string does not have a suffix |
regex($value, $pattern, $message = '') | Check that a string matches a regular expression |
notRegex($value, $pattern, $message = '') | Check that a string does not match a regular expression |
unicodeLetters($value, $message = '') | Check that a string contains Unicode letters only |
alpha($value, $message = '') | Check that a string contains letters only |
digits($value, $message = '') | Check that a string contains digits only |
alnum($value, $message = '') | Check that a string contains letters and digits only |
lower($value, $message = '') | Check that a string contains lowercase characters only |
upper($value, $message = '') | Check that a string contains uppercase characters only |
length($value, $length, $message = '') | Check that a string has a certain number of characters |
minLength($value, $min, $message = '') | Check that a string has at least a certain number of characters |
maxLength($value, $max, $message = '') | Check that a string has at most a certain number of characters |
lengthBetween($value, $min, $max, $message = '') | Check that a string has a length in the given range |
uuid($value, $message = '') | Check that a string is a valid UUID |
ip($value, $message = '') | Check that a string is a valid IP (either IPv4 or IPv6) |
ipv4($value, $message = '') | Check that a string is a valid IPv4 |
ipv6($value, $message = '') | Check that a string is a valid IPv6 |
email($value, $message = '') | Check that a string is a valid e-mail address |
notWhitespaceOnly($value, $message = '') | Check that a string contains at least one non-whitespace character |
File Assertions
Method | Description |
---|---|
fileExists($value, $message = '') | Check that a value is an existing path |
file($value, $message = '') | Check that a value is an existing file |
directory($value, $message = '') | Check that a value is an existing directory |
readable($value, $message = '') | Check that a value is a readable path |
writable($value, $message = '') | Check that a value is a writable path |
Object Assertions
Method | Description |
---|---|
classExists($value, $message = '') | Check that a value is an existing class name |
subclassOf($value, $class, $message = '') | Check that a class is a subclass of another |
interfaceExists($value, $message = '') | Check that a value is an existing interface name |
implementsInterface($value, $class, $message = '') | Check that a class implements an interface |
propertyExists($value, $property, $message = '') | Check that a property exists in a class/object |
propertyNotExists($value, $property, $message = '') | Check that a property does not exist in a class/object |
methodExists($value, $method, $message = '') | Check that a method exists in a class/object |
methodNotExists($value, $method, $message = '') | Check that a method does not exist in a class/object |
Array Assertions
Method | Description |
---|---|
keyExists($array, $key, $message = '') | Check that a key exists in an array |
keyNotExists($array, $key, $message = '') | Check that a key does not exist in an array |
validArrayKey($key, $message = '') | Check that a value is a valid array key (int or string) |
count($array, $number, $message = '') | Check that an array contains a specific number of elements |
minCount($array, $min, $message = '') | Check that an array contains at least a certain number of elements |
maxCount($array, $max, $message = '') | Check that an array contains at most a certain number of elements |
countBetween($array, $min, $max, $message = '') | Check that an array has a count in the given range |
isList($array, $message = '') | Check that an array is a non-associative list |
isNonEmptyList($array, $message = '') | Check that an array is a non-associative list, and not empty |
isMap($array, $message = '') | Check that an array is associative and has strings as keys |
isNonEmptyMap($array, $message = '') | Check that an array is associative and has strings as keys, and is not empty |
Function Assertions
Method | Description |
---|---|
throws($closure, $class, $message = '') | Check that a function throws a certain exception. Subclasses of the exception class will be accepted. |
Collection Assertions
All of the above assertions can be prefixed with all*()
to test the contents
of an array or a \Traversable
:
Assert::allIsInstanceOf($employees, 'Acme\Employee');
Nullable Assertions
All of the above assertions can be prefixed with nullOr*()
to run the
assertion only if it the value is not null
:
Assert::nullOrString($middleName, 'The middle name must be a string or null. Got: %s');
Extending Assert
The Assert
class comes with a few methods, which can be overridden to change the class behaviour. You can also extend it to
add your own assertions.
Overriding methods
Overriding the following methods in your assertion class allows you to change the behaviour of the assertions:
public static function __callStatic($name, $arguments)
- This method is used to 'create' the
nullOr
andall
versions of the assertions.
- This method is used to 'create' the
protected static function valueToString($value)
- This method is used for error messages, to convert the value to a string value for displaying. You could use this for representing a value object with a
__toString
method for example.
- This method is used for error messages, to convert the value to a string value for displaying. You could use this for representing a value object with a
protected static function typeToString($value)
- This method is used for error messages, to convert the a value to a string representing its type.
protected static function strlen($value)
- This method is used to calculate string length for relevant methods, using the
mb_strlen
if available and useful.
- This method is used to calculate string length for relevant methods, using the
protected static function reportInvalidArgument($message)
- This method is called when an assertion fails, with the specified error message. Here you can throw your own exception, or log something.
Static analysis support
Where applicable, assertion functions are annotated to support Psalm's Assertion syntax. A dedicated PHPStan Plugin is required for proper type support.
Authors
Contribute
Contributions to the package are always welcome!
- Report any bugs or issues you find on the issue tracker.
- You can grab the source code at the package's Git repository.
License
All contents of this package are licensed under the MIT license.
Top Related Projects
Thin assertion library for use in libraries and business-model
The PHP Unit Testing framework.
Data transfer objects with batteries included
🔰 Instant PHP quality checks from your console
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual Copilot