The most awesome validation engine ever created for PHP
Changes from last version: https://github.com/Respect/Validation/compare/2.3.6...2.3.7
Changes from last version: https://github.com/Respect/Validation/compare/2.3.5...2.3.6
Changes from last version: https://github.com/Respect/Validation/compare/2.3.4...2.3.5
Versioning Changes:
Deprecations:
Fixes:
KeySet now reports which extra keys are causing the rule to fail.Changes:
KeySet in Not.Phone now uses giggsey/libphonenumber-for-php, this package needs
to be installed if you want to use this validator.Phone now supports the parameter $countryCode to validate phones
of a specific country.Versioning Changes:
Deprecations:
Fixes:
KeySet now reports which extra keys are causing the rule to fail.Changes:
KeySet in Not.Phone now uses giggsey/libphonenumber-for-php, this package needs
to be installed if you want to use this validator.Phone now supports the parameter $countryCode to validate phones
of a specific country.The Respect team is proud to announce the release of Respect\Validation 2.24 🐼 This version is also already available on packagist.
This is a dusting-off release with most of the PRs since 2.2.3 being merged, compatibility for newer PHP versions adjusted and a new lead maintainer (@alganet, which is the original library author).
It is expected that 2.2.4 will be the last release of the 2.2.x series, with 2.3 following soon after.
Feedback and bug reports are highly appreciated. Feel free to get in touch either via Issues or Discussions.
Happy Validatin'
Meta:
Versioning Changes:
Deprecations:
Fixes:
v::decimal() for float values (thanks @scruwi)v::portugueseNif() to validate Número de Identificação Fiscal in Portugal (thanks @goncalo-andrade).v::intval() now handles negative values with trailing zeroes better (thanks @l-x)Drop support for PHP 7.2.
The Respect development team announces the immediate availability of Respect\Validation 2.0.0.
This release adds nineteen new rules, improvements, and bug fixes.
This version is been in the master branch for a long time, it’s not perfect, but it is good enough.
We would like to thanks to all the developers who spent their free time to contribute to this project. Without you, this release would be impossible. Especially:
Also, Jetbrains for providing a License that allowed me to refactor a lot faster using PHPStorm.
This version (2.0) has more than 8k backward compatibility breaks 1 with the last version (1.1). Most of them, are all the classes becoming final and public properties becoming private, but there are some other big ones. All those backward compatibility breaks help Validation to be easier to maintain, allowing us to release more and more often.
Below a more detailed list of the main backward compatibility breaks:
There are many reasons why classes should be final 2. Most classes we have are self-contained, and there are not many cases that inheritance is necessary. We want to encourage users to use them to use composition rather than inheritance, especially if we are talking about the rules, and for that same reason, we are also focusing on making their APIs clearer.
Public properties are one of the enemies of maintainability because they make the objects mutable and unpredictable. With them, we cannot ensure an object has a valid state, and we need to validate the properties before using them. Besides, changing a property name is a background compatibility break.
In this version, the whole codebase uses PHP 7.1 type-hinting. They are also using strict typing.
In the last versions, those methods were supposed to return a boolean value or throw an exception. However, in practice, those methods throw an exception when the validation fails and return TRUE when the validation passes.
In this version, those methods don't return any value: when it throws an exception it means that the validation failed; when they don't throw an exception it means that the validation passed.
After trying to fix its behavior many times, it was clear that the method itself was very confusing. Also, it became unnecessary due to how Validation evolved during the development of version 2.0.
In older versions, that method is mainly used to translate, customize templates, and retrieve the messages in an array structure.
In this version, users can configure a global translator in the Factory. As for the customization and to retrieve the messages in an array structure, users can use "NestedValidationException::getMessages()" that does a much better job.
Because of the reasons mentioned above, and for the fact that "NestedValidationException::findMessages()" is so high maintenance as a consequence of all its edge cases, it made sense to remove it from the codebase.
In the previous versions, user could overwrite Validation rules using with(), not they can’t./
In the last version, the OneOf rule validation passes if any assigned rule validation passes. In this version, the OneOf rule validation pass if only one of the assigned rule validation passes.
We also created the AnyOf rule in which the validation passes if any assigned rule validation passes.
In the last version, the Date rule validation passes if the input is a date, time, or date and time. However, it does not provide a way to be specific about the validation of date or time.
In this version, the Date rule validation passes only if the input is a date. We also created a Time rule to validate time, and a DateTime rule to validate date and time (as Date used to be).
In the last version, Min, Max, and Between allow users to define whether the validation is inclusive or exclusive with a boolean value in their constructor. Those boolean values not made the complexity or those rules higher, but also confusing sometimes.
In this version, the validation of those rules is always inclusive, and to use Between you need it is necessary to provide both minimum and maximum values. To help with non-inclusive validation we created LessThan and GreaterThan rules.
In this version, the Each rule can validate both keys and values of the input. In this version, the Each rule can only validate the values of the input.