Download the PHP package ohtyap/laravel-sane-validator without Composer
On this page you can find all versions of the php package ohtyap/laravel-sane-validator. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download ohtyap/laravel-sane-validator
More information about ohtyap/laravel-sane-validator
Files in ohtyap/laravel-sane-validator
Package laravel-sane-validator
Short Description sane validation rule handling for laravel
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package laravel-sane-validator
laravel-sane-validator
This is a strongly opinionated patch of laravel's validator. When using the validator outside
of an HTTP POST scope (e.g., validating some data structures), you might notice some
shortcomings and unexpected behaviors from the validator. laravel-sane-validator tries
fixing them.
Installation
Install the package via composer:
After that, declare to use laravel-sane-validator by setting the resolver in the validation factory:
Shortcomings of laravel's validator
The first shortcoming is how the validator is handling implicit rules in combination of empty strings. The following quote is taken from the laravel documentation:
By default, when an attribute being validated is not present or contains an empty string, normal validation rules, including custom rules, are not run.
This has the effect that input data might bypass your validation - especially when it comes to optional fields.
In the above example, the expectation would be that the validator fails because the input (a space)
isn't (obviously) not a valid email address.
It's possible to enforce the validation of empty strings by using the required or filled rule. This is
not very intuitive for optional fields, and it is very easy to forget to add filled (or sometimes|required).
Moreover, this brings the second shortcoming: laravel is making assumptions about how a non-empty value should
look. It is impossible to pass null or [] - even if both are perfectly valid values - when using required.
Consequently, combinations like required|nullable aren't possible.
laravel-sane-validator behavior
When using this validator, implicit rules are always executed when the field is present in the input. That way, it is no longer possible for empty strings to bypass validation.
required (including the other special cases of required* like requiredIf ) has the same behavior
as present. It's only checking if the field is present in the input. More explicit evaluation of what is
considered valid is up to the developer and what is defined in the rules.
Special note about filled
filled is using the same behavior as in the original validator. An empty string is still considered
invalid (same for an empty array, null, etc.). But it is possible to declare rules like filled|nullable.
Strategies to start using laravel-sane-validator
By default you install and register laravel-sane-validator and you are good to go. But this might be troublesome
for existing and bigger application. A step-by-step approach might be a better way of changing the behavior of the
validation.
