Laravel Validation Rules Only Latin

Laravel Validation Rules Only Latin

By Plan

Enterprise

Teams

Compare all

By Solution

CI/CD & Automation

DevOps

DevSecOps

Case Studies

Customer Stories

Resources

In this organization

All GitHub

↵

In this organization

All GitHub

↵

Search

All GitHub

↵

In this organization

All GitHub

↵

A collection of Laravel 5 validation engine rules.

1
follower

https://laravel-validation-rules.github.io

All

Public

Sources

Forks

Archived

Mirrors

Templates

All

HTML

PHP

Last updated

Name

Stars

PHP

22

Apache-2.0

8

0

0

Updated Sep 18, 2022

PHP

24

Apache-2.0

4

1

3

Updated Aug 17, 2022

PHP

187

Apache-2.0

53

5

2

Updated Feb 24, 2022

PHP

21

Apache-2.0

4

0

0

Updated Feb 22, 2022

PHP

64

Apache-2.0

9

0

0

Updated Feb 9, 2022

PHP

12

Apache-2.0

6

1

2

Updated Feb 8, 2022

PHP

31

Apache-2.0

9

0

1

Updated Feb 8, 2022

PHP

15

Apache-2.0

2

0

0

Updated Dec 28, 2021

PHP

2

Apache-2.0

1

0

0

Updated Sep 16, 2020

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session.
You signed out in another tab or window. Reload to refresh your session.

The laravel-validation-rules website.

A README for the organisation and its repositories.

Validate a subdomain for your saas application

Validates 2 & 3 character country codes.

Validate a subdomain for your saas application

Validate that a given timezone is valid.

Validate US States and Canada Provinces

Validate if an ip address is public or private.

The laravel-validation-rules website.

This organization has no public members. You must be a member to see who’s a part of this organization.

< input v-validate = " ' date_format:dd/MM/yyyy|after:afterTarget ' " name = " after_field " type = " text " >

< input name = " after_field_target " ref = " afterTarget " type = " text " >

< input v-validate = " ' alpha ' " name = " alpha_field " type = " text " >

< input v-validate = " ' alpha_dash ' " name = " alpha_dash_field " type = " text " >

< input v-validate = " ' alpha_num ' " name = " alpha_num_field " type = " text " >

< input v-validate = " ' alpha_spaces ' " name = " alpha_spaces_field " type = " text " >

< input v-validate = " ' date_format:dd/MM/yyyy|before:beforeTarget ' " name = " before_field " type = " text " >

< input name = " before_field_target " ref = " beforeTarget " type = " text " >

< input v-validate = " ' between:1,11 ' " name = " between_field " type = " text " >

< input v-validate = " ' required ' " name = " password " type = " password " :class = " { ' is-danger ' : errors.has( ' password ' )} " placeholder = " Password " ref = " password " >
< span v-show = " errors.has( ' password ' ) " class = " help is-danger " > {{ errors.first('password') }}

< input v-validate = " ' required|confirmed:password ' " name = " password_confirmation " type = " password " :class = " { ' is-danger ' : errors.has( ' password_confirmation ' )} " placeholder = " Password, Again " data-vv-as = " password " >
< span v-show = " errors.has( ' password_confirmation ' ) " class = " help is-danger " > {{ errors.first('password_confirmation') }}

< input v-validate = " ' credit_card ' " name = " credit_field " type = " text " >

< input v-validate = " ' date_format:dd/MM/yyyy|date_between:10/09/2016,20/09/2016 ' " name = " date_between_field " type = " text " >

< input v-validate = " ' date_format:dd/MM/yyyy ' " name = " date_format_field " type = " text " >

< input v-validate = " ' decimal:3 ' " name = " decimal_field " type = " text " >

< input v-validate = " ' digits:3 ' " name = " digits_field " type = " text " >

< input v-validate = " ' dimensions:30,30 ' " data-vv-as = " image " name = " dimensions_field " type = " file " >

< input v-validate = " ' email ' " data-vv-as = " email " name = " email_field " type = " text " >

< input v-validate = " ' ext:jpeg,jpg ' " data-vv-as = " field " name = " ext_field " type = " file " >

< input v-validate = " ' image ' " data-vv-as = " image " name = " image_field " type = " file " >

< span class = " select " >
< select v-validate = " ' included:1,2,3 ' " name = " in_field " data-vv-as = " selected " >
< option value = " 1 " > One
< option value = " 2 " > Two
< option value = " 3 " > Three
< option value = " 4 " > Invalid

< input v-validate = " ' ip ' " data-vv-as = " ip " name = " ip_field " type = " text " >

< input v-validate = " ' ip ' " data-vv-as = " host_address " name = " host_address_field " type = " text " >

< input v-validate = " { is: confirmation } " type = " text " name = " password " >
< input v-model = " confirmation " type = " text " name = " password_confirmation " >

< input v-validate = " { is_not: duplicate } " type = " text " name = " field " >
< input v-model = " duplicate " type = " text " name = " not_again " >

< input v-validate = " ' length:5 ' " type = " text " name = " field " >

< input v-validate = " ' max:11 ' " data-vv-as = " field " name = " max_field " type = " text " >

< input v-validate = " ' max_value:9000 ' " data-vv-as = " field " name = " max_value_field " type = " text " >

< input v-validate = " ' mimes:image/* ' " data-vv-as = " image " name = " mimes_field " type = " file " >

< input v-validate = " ' min:3 ' " data-vv-as = " field " name = " min_field " type = " text " >

< input v-validate = " ' min_value:10 ' " data-vv-as = " field " name = " min_value_field " type = " text " >

< span class = " select " >
< select v-validate = " ' excluded:1,2,3 ' " name = " not_in_field " data-vv-as = " selected " >
< option value = " 1 " > One - Invalid
< option value = " 2 " > Two - Invalid
< option value = " 3 " > Three - Invalid
< option value = " 4 " > Four - Valid

< input v-validate = " ' numeric ' " data-vv-as = " field " name = " numeric_field " type = " text " >

< input v-validate = " { required: true, regex: /\.(js|ts)$/ } " name = " regex " >

< input v-validate = " ' required ' " data-vv-as = " field " name = " required_field " type = " text " >

United States of America Federated States of Micronesia Other country
< select ref = " country " v-validate :class = " { ' input ' : true, ' is-danger ' : errors.has( ' required_field ' ) } " name = " select_country " >
< option value = " US " > United States
< option value = " OTHER " > Other country

< input v-validate.immediate = " ' required_if:country,US,FM ' " data-vv-as = " state " :class = " { ' input ' : true, ' is-danger ' : errors.has( ' state_field ' ) } " name = " state_field " type = " text " placeholder = " State " >
< span v-show = " errors.has( ' state_field ' ) " class = " help is-danger " > {{ errors.first('state_field') }}

< input v-validate = " ' size:10 ' " name = " size_field " data-vv-as = " file " type = " file " >

< input v-validate = " {url: {require_protocol: true }} " data-vv-as = " field " name = " url_field " type = " text " >

VeeValidate comes with a bunch of validation rules out of the box and they are all localized and cover most validation needs:
The field under validation must have a valid date and is after the date value in the target field.
Target based rules like after , before , and confirmed can target custom components as well as native inputs, but the target field must have a ref attribute set and the confirmed parameter must be the same ref value. For validation providers the target field must have a vid prop set instead of the ref .
The field under validation may only contain alphabetic characters.
The field under validation may contain alphabetic characters, numbers, dashes or underscores.
The field under validation may contain alphabetic characters or numbers.
The field under validation may contain alphabetic characters or spaces.
The field under validation must have a valid date and is before the date value in the target field.
Target based rules like after , before , and confirmed can target custom components as well as native inputs, but the target field must have a ref attribute set and the confirmed parameter must be the same ref value. For validation providers the target field must have a vid prop set instead of the ref .
The field under validation must have a numeric value bounded by a minimum value and a maximum value.
The field under validation must have the same value as the confirmation field.
Target based rules like after , before , and confirmed can target custom components as well as native inputs, but the target field must have a ref attribute set and the confirmed parameter must be the same ref value. For validation providers the target field must have a vid prop set instead of the ref .
Make use of the data-vv-as="password" attribute for the confirmation field. The value input for this attribute is used as the field label in the error message. This way you can reuse the password name to show either an error with the password or password_confirmation field.
The field under validation must be a valid credit card.
The field under validation must be a valid date between the two dates specified.
The field under validation must be a valid date in the specified format. This rule must be present when using any date rule.
The field under validation must be numeric and may contain the specified amount of decimal points.
The field under validation must be numeric and have the specified number of digits.
The file added to the field under validation must be an image (jpg,svg,jpeg,png,bmp,gif) having the exact specified dimension.
The field under validation must be a valid email.
Email rule can recieve any args from validator.js isEmail validator. Note that to be able to configure it you need to use the object format.
The file added to the field under validation must have one of the extensions specified.
The file added to the field under validation must have an image mime type (image/*).
The field under validation must have a value that is in the specified list.
The field under validation must have a string that is a valid ipv4 value.
The field under validation must have a string that is a valid ipv4 value, a valid ipv6 value, or a valid fully-qualified domain name.
The field under validation must be equal to the first argument passed, uses === for equality checks. This rule is useful for confirming passwords when used in object form. Note that using the string format will cause any arguments to be parsed as strings, so use the object format when using this rule.
A negated version of is rule, also uses the === for equality checks.
The field under validation must be an iterable and/or have a length property of the specified amount. If another value is provided it forces the length check to be between those values in a min/max fashion.
The field under validation length may not exceed the specified length.
The field under validation must be a numeric value and must not be greater than the specified value.
The file type added to the field under validation should have one of the specified mime types.
You can use '*' to specify a wild card, something like mimes:image/* will accept all image types.
The field under validation length should not be less than the specified length.
The field under validation must be a numeric value and must not be less than the specified value.
The field under validation value should not be in the specified list.
The field under validation must only consist of numbers.
The field under validation must match the specified regular expression.
You should not use the pipe '|' or commas ',' within your regular expression when using the string rules format as it will cause a conflict with how validators parsing works. You should use the object format of the rules instead.
The field under validation must have a non-empty value. By default, all validators pass the validation if they have "empty values" unless they are required. Those empty values are: empty strings, undefined , null .
By default, the boolean value of false will pass validate. Setting invalidateFalse to true will fail validation for false values. For example, using v-validate="'required:true'" is helpful to support pseudo-checkbox validations where the checkbox must be checked. Note that automatically supports this scenario.
The required & required_if rules are special, by default the validator skips the validation for non-required fields that have an empty value. If you wish to force validation for non-required fields, use the continues modifier .
The field under validation must have a non-empty value only if the target field (first argument) is set to one of the specified values (other arguments).
In the example below, the required_if:country,US,FM rule makes the state field required only if the ref="country" input is set to US or FM.
If the target field value meets the requirement, empty values (empty strings, undefined , null and false ) in the field under validation will trigger an error.
The file size added to the field under validation must not exceed the specified size in kilobytes.
The field under validation must be a valid url. Protocols are not required by default.
This rule can recieve any args from validator.js isURL validator. Note that to be able to configure it you need to use the object for
Hard Porn Photo
Kinky Kicks Ballbusting
Flat Heels

Laravel Validation Rules Only Latin

Report Page