Versions

• vee-validate: 3.1.3
• vue: 2.6.10
• vue-jest: 3.0.5
• @vue/test-utils: ^1.0.0-beta.31

Describe the bug
I have a BaseInput.vue component which has one default <slot></slot> wrapped in a <validation-provider>. When it has errors it will show the error message inside a <div class="error-message"></div>.
But, in my tests, when I pass a <input> to the default slo

type Item struct {
	Bt int `valid:"range(1|100)"`
}

func main() {
	t := Item{-1}
	ok, err := govalidator.ValidateStruct(t)
	fmt.Println(ok, err)
}

output:Bt: Validator range(1|100) doesn't support kind int;

When reading pattern from HTML it is used directly as a regular expression, which is not correct. The spec says

The compiled pattern regular expression, when matched against a string, must have its start anchored to the start of the string and its end anchored to the end of the string.

This implies that the regular

The current master README on the front-page of this github repo is misleading with respect to isValidHostname as it points to unreleased changes that deprecate isValid and introduce isValidHostname… However those changes are still unreleased.

So if users of the latest tldjs@2.3.1 come to this repo and check out the readme they might easily get confused.

How about releasing a new vers

Similar to issue #18, add methods in the collection_ktx package.

Improve JsDoc to support suggestions in VScode.

Inspiration: #10 and #12.

Is there any documentation on using valiktor with @WebMvcTest based Spring tests?

I've added @Import(ValiktorAutoConfiguration::class, ValiktorWebMvcAutoConfiguration::class) but it doesn't seem to use the valiktor constraint violation exception handlers.

I have defined rules like so (two places, becasue I am unsure which -- not clear according to documentation):

	['nuxt-validate', {
		lang: 'en',
		rules: ['email', 'min', 'max', 'confirmed', 'numeric'],
		nuxti18n: {
			locale: {
				'da': 'da',
				'en': 'en'
			},
			rules: ['email', 'min', 'max', 'confirmed', 'numeric']
		},
		mode: 'eager',
		classes: {
			valid: 'i

Validar uma lista de tuplas de documentos.

A seguir, consta um jeito de como essa funcionalidade deve funcionar:

from validate_docbr as docbr


# Documentos
documentos = [
    (docbr.CPF, "012.345.678-90"),
    (docbr.CNPJ, "01.234.567/8901-23"),
    (docbr.CPF, "01234567891"),
]

# Validar documentos
validacoes = docbr.validate_docs( documentos )
# Output
# [True, Fals

Is your feature request related to a problem? Please describe.

There are no samples for WPF, Windows Forms and UWP now. Let's fix that.

Describe the solution you'd like

We should create samples for WPF and WF.

Describe suggestions on how to achieve the feature

Probably we should port existing XF sample to WPF and WF.

Worth [sharing existing view models](https://github

Okay, so if you pass a filterWith rule, that function should return true|false.

However, you can throw a custom error in that function instead. It's just that the customer error needs to implement toJSON and return { field, message }.