For the complete documentation index, see llms.txt. This page is also available as Markdown.

Using existing validators

KASKO Frontend Framework utilizes most of Laravel Validators with the addition of some KASKO validators. These validation rules are defined in field definitions.

Note: See "Adding Custom Validators" for more information how to add product-specific custom validators.

Available data types (variables will be converted prior to sending to the API, but are not validated in frontend):

  • number - Decimal numbers (alias: numeric)

  • numeric - Decimal numbers (alias of number)

  • iso_date - Date (YYYY-MM-DD format)

  • iso_datetime - Date + time

  • email - Email address

  • phone_number - Phone number

  • dataset - Dataset reference

Available KASKO Validators

alnum_dash

Alpha-numeric characters and dash is allowed.

alnum_dash_slash

Alpha-numeric characters, dash and forward slash is allowed.

alnum_space

Alpha-numeric characters and space is allowed.

contains_blacklist_string

Fails validation if the given input matches a value in the blacklist.

Value
Validation passes?

1hello

No

This is my hello text.

No

contains_exact_blacklist_string

Fails validation if the given input exactly matches a value in the blacklist (full words).

Value
Validation passes?

1hello

Yes

This is my hello text.

No

divisible_without_remainder

Check if the input value is divisible by X without a remainder.

Value
Validation passes?

123

No

12300

Yes

each_word_capitalized

Check if each word in the input is capitalized.

Value
Validation passes?

hello World

No

Hello World

Yes

iso_date

Check if the input is a valid ISO 8601 date.

iso_datetime

Check if the input is a valid ISO 8601 datetime.

required_false

Input must be false to pass the validation.

required_false_if

Input must be false if additional field match the given value.

required_if_all_false

Input under validation is required if all other (given) fields are false.

required_if_and

Input under validation is required if all other (given) fields match the given values.

required_true

Deprecated: required_true should no longer be used because there is no backend support for it. Please use the accepted validation rule instead.

Input must be true to pass the validation.

required_true_if

Input must be true if additional field match the given value.

required_true_if_and

Input must be true if all other (given) fields match the given values.

sequential_char_limit

Check if input doesn't have more than (given) limit of sequential characters.

iban

Check if input has a valid iban code, for this validation we are using 3rd party library.

First check is done by our framework:

  • can contain only A-Z and 0-9 (letters and numbers)

Next are 3rd party library checks:

  • check if first 2 chars from IBAN is registered in 3rd party library's supported country codes list. You can find this list here.

  • if is, then check against selected country's IBAN length

  • check against selected country's IBAN structure

  • and then check and calculate MOD 97-10 of the passed IBAN as specified in ISO7064

bic

Check if input has a valid bic code.

Code should consist from 8 to 11 chars. First 6 chars should be A-Z, next 2 should be A-Z or 0-9 and then last 3 are optional which should be A-Z or 0-9.

imei

Check if input has a valid IMEI code - consists of 15 digits and is valid using Luhn formula.

phone_number

Check if input has a valid phone number

interval_before

Check if input value (date) is between the given time interval.

value must be between time period trip_start_date and +91 days

interval_before_or_equal

Check if input value (date) is between the given time interval or equal.

interval_after

Check if input value (date) is between the given time interval.

value must be between time period -100 years and policy_start_date

interval_after_or_equal

Check if input value (date) is between the given time interval or equal.

keyword_blacklist

Fails validation if the given input matches a value in the blacklist. Validation is case sensitive and blacklisted keyword can be a sentence.

Value
Validation passes?

1hello

Yes

This is my hello text.

No

sometext

Yes

Need to write some text.

No

. hello world

No

all_caps

Check if each letter in the input is capitalized.

not_all_caps

Input value (string) can't have all capital letters.

Value
Validation passes?

HeLLo WorLD

Yes

HELLO WORLD

No

year

Input is validated against the provided rule which contains two arguments - a comparison operator and year.

accepted

Input must be accepted (truthy value like yes, on, 1, true). Used for consent fields.

accepted_if

Input must be accepted if another field matches the given value.

accepted_if_and

Input must be accepted if all other (given) fields match the given values.

alpha

Only alphabetic characters are allowed.

case_sensitivity

Case-sensitive matching validation.

compare

Compare two fields using an operator.

exclude_unless

Exclude field from validation unless another field matches the given value. If condition is not met, the field is excluded from the request.

exclude_unless_and

Exclude field from validation unless all conditions are met.

payment

Payment-specific validation for payment fields.

Last updated