6.0.0

What's Changed

• Laravel 11 support #32
• Remove support for PHP 8.0

Full Changelog: 5.0.0...6.0.0

5.0.0 (Laravel 9 support)

What's Changed

• L9 integration PR by @rjvandoesburg in #30

Dropping support for Laravel 7 and PHP 7.*

If you use Laravel 7 or PHP 7., you should stick to the 4. branch. Going forward, these releases will no longer be supported.

Full Changelog: 4.0.2...5.0.0

4.0.2

Full Changelog: 4.0.1...4.0.2

4.0.1

What's Changed

• Implement CarbonDateSanitizer by @arondeparon in #27

Full Changelog: 4.0...4.0.1

Release 4.0

This is backwards incompatible release if you use Laravel 6.

This new major release will only support Laravel 7 and beyond. If you need Laravel 6 you should pick the latest available 3.x version.

Release 3.1.1

This is a backwards compatible patch release.

This release replaces the strtolower, strtoupper and ucfirst functions with their Laravel equivalents using the Str:: helpers. This has the benefit of being unicode compatible (mb_ functions are used under the hood.)

Thanks @jaulz!

Release 3.1.0

This release implements support for PHP 8 (#22).

Thanks @erickmcarvalho !

Release 3.0.1

Bugfixes

• Fixes a bug that caused multiple sanitizers not to be chained, but rather to overwrite each other. Thanks @johnpaulmedina !

Release 3.0

This release implements support for Laravel 8.

Important:

Laravel 8 comes with a minimum requirement of PHP 7.3. Since previous releases supported PHP 7.2, the 3.0 is a major upgrade.

If you are stuck on PHP 7.2 (or even older), you should stick with 2.x.

Release 2.3

This releases changes behaviour to be more compliant with Laravel's standards.

After a FormRequest instance has resolved in the application container, the validator will be automatically called. Before the validation runs, prepareForValidation() is triggered which has the purpose of altering request data before it enters validation, which is exactly what this package does! 🔥

This tests also borrow a lot of test scaffolding from Laravel's internal testing, because it is not trivial to create a FormRequest object without initialising the entire application.

There should be no impact on end users, since the sanitizer was previously also automatically called once validation started. Now, it just does it in a more compliant way 😊