Download the PHP package bllim/laravalid without Composer
On this page you can find all versions of the php package bllim/laravalid. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download bllim/laravalid
More information about bllim/laravalid
Files in bllim/laravalid
Package laravalid
Short Description This package makes validation rules defined in laravel work client-side by converting to html/js plugins such as jquery validation. It also allows to use laravel validation messages so you can show same messages for both sides.
License MIT
Informations about the package laravalid
Laravalid
Laravel Validation For Client Side
This package makes validation rules defined in laravel work client-side by converting to html/js plugins such as jquery validation. It also allows to use laravel validation messages so you can show same messages for both sides.
Table of contents
- Feature Overview
- Installation
- Configuration
- Usage
- Extending
- Plugins and Supported Rules
- Known Issues
- To Do
- Contributors
- Licence
Feature Overview
- Multi-Plugin Support //For now, there is just one :)
Jquery Validation
- Extendible
- Laravel form builder based
- Validation rules can be set from controller
- Distinguishing between numeric input and string input
- User friendly input names
- Remote rules such as unique and exists
Installation
Require bllim/laravalid
in composer.json and run composer update
.
Note: For Laravel 4 use
laravel4
branch like as"bllim/laravalid": "dev-laravel4"
or"~0.9"
Composer will download the package. After the package is downloaded, open config/app.php
and add the service provider and alias as below:
Also you need to publish configuration file and assets by running the following Artisan commands.
Configuration
After publishing configuration file, you can find it in config
folder as laravalid.php
file. Configuration parameters are as below:
Parameter | Description | Values |
---|---|---|
plugin | Choose plugin you want to use | See Plugins and Supported Rules |
useLaravelMessages | If it is true, laravel validation messages are used in client side otherwise messages of chosen plugin are used | true/false |
route | Route name for remote validation | Any route name (default: laravalid) |
Usage
The package uses laravel Form Builder to make validation rules work for both sides. Therefore you should use Form Builder. While opening form by using Form::open
you can give $rules
as second parameter:
Also if you don't want to struggle with $rules
at view files, you can set it in Controller
or route with or without form name by using Form::setValidation($rules, $formName)
. If you don't give form name, this sets rules for first Form::open
For rules which is related to input type in laravel (such as max
, min
), the package looks for other given rules to understand which type is input. If you give integer or numeric as rule with max
, min
rules, the package assume input is numeric and convert to data-rule-max
instead of data-rule-maxlength
.
The converter assume input is string
by default. File type is also supported.
Validation Messages
Converter uses validation messages of laravel (resources/lang/en/validation.php
) by default for client-side too. If you want to use jquery validation messages, you can set useLaravelMessages
, false in config file of package which you copied to your config dir.
Plugins
Jquery Validation
While using Jquery Validation as html/js validation plugin, you should include jquery.validate.laravalid.js
in your views, too. After assets published, it will be copied to your public folder. The last thing you should do at client side is initializing jquery validation plugin as below:
Example
Controller/Route side
View side
Extending
There are two ways to extend package with your own rules. First, you can extend current converter plugin dynamically like below:
Second, you can create your own converter (which extends Base\Converter
or any current plugin converter) in Bllim\Laravalid\Converter\
namespace and change plugin configuration in config file with your own plugin name.
Note: If you are creating a converter for some existed html/js plugin please create it in
Converter
folder and send a pull-request.
Plugins and Supported Rules
Jquery Validation
To use Jquery Validation, change plugin to JqueryValidation
in config file and import jquery
, jquery-validation
and jquery.validate.laravalid.js in views.
Rules | Jquery Validation |
---|---|
Accepted | - |
Active URL | + |
After (Date) | + |
Alpha | + |
Alpha Dash | - |
Alpha Numeric | + |
Array | - |
Before (Date) | + |
Between | + |
Boolean | - |
Confirmed | - |
Date | + |
Date Format | - |
Different | + |
Digits | - |
Digits Between | - |
+ |
|
Exists (Database) | + |
Image (File) | + |
In | - |
Integer | + |
IP Address | + |
Max | + |
MIME Types | + |
Min | + |
Not In | - |
Numeric | + |
Regular Expression | + |
Required | + |
Required If | - |
Required With | + |
Required With All | - |
Required Without | + |
Required Without All | - |
Same | + |
Size | - |
String | - |
Timezone | - |
Unique (Database) | + |
URL | + |
Note: It is easy to add some rules. Please check
Rule
class of related converter.
Contribution
You can fork and contribute to development of the package. All pull requests is welcome.
Conversion Logic
Package converts rules by using converters (in src/Bllim/Laravalid/Converter
). It uses Converter
class of chosen plugin which extends Converter/Base/Converter
class.
You can look at existed methods and plugins to understand how it works. Explanation will be ready, soon.
Known issues
- Some rules are not supported for now
TODO
- Support unsupported rules
- Improve doc
- Comment code
Contributors
- @bllim
- @phpspider
- @jannispl
- @rene-springmann
- @nthachus
and more
License
Licensed under the MIT License
All versions of laravalid with dependencies
laravelcollective/html Version ~5.0
illuminate/support Version ~5.0
illuminate/validation Version ~5.0
illuminate/routing Version ~5.0
illuminate/translation Version ~5.0