e.g. isPassportNumber, etc.

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

This is an issue with the documentation.

**The version of Ajv you are using

Validator::CurrencyCode()->validate('')
The behavior of this validation changes from v1.1.29 to v1.1.31.

valid-1.1.29: Validator::CurrencyCode()->validate('') RESULT : FALSE
valid-1.1.31: Validator::CurrencyCode()->validate('') RESULT : TRUE

This should be documented somewhere, it took a while to find out.

With this vulnerability, an attacker can bypass any security checks enforced by class-validator.

When class-validator is used to validate user-input, the attributes in the user-input object will be transformed into the validation class instance.
However, the transforming procedure will overwrite the internal attribute of validation class instance (e.g., constructor attribute) if the attacke

Hi guys. Is there any documentation for the methods found in ShaderLang.h?
For example,what does TShader::setInvertY do?
I have just started so pretty sure I am going to have more questions related to the API.

check if NNNNNNN-DD.AAAA.JTR.OOOO is valid.

ref: CNJ unifica numeração de processos em todo o país

Hi,
How can we use this package in the validate method of mongoosejs? (like validator.js or @hapi/joi)

const mongoose = require('mongoose');
const validator = require('validator');

const userSchema = new mongoose.Schema({
  name: {
    type: String,
    required: [true, 'A tour must have a name'],
     validate: [validator.isAlpha, 'name must only contain characters']
  },
  p

The current code coverage is very low, we need to add more unit tests.

Currently the example value can have a different data structure that is defined in the schema and the swagger-cli validate doesn't rise an error.

example:
    foo:
        bar: a
        baz: b
type: object
properties:
    foo:
        type: integer
        format: int32
        default: 0

I think it would be very useful if the example value would be validated against

• Guidance on adding a linter new rule-action (if none of the existing ones can perform the action, or be extended)
• Expand on guidelines re: keeping commits to logical areas of the code / individual packages where possible
• Use of conventional-commit standard going forward
• Advice not to include any package-lock.json changes PRs, for security reasons. File will be regene

There is an issue on this page:

https://indicative-v5.adonisjs.com/docs/requiredwithoutany

Should it be?

Ensures the field is required when any of the other fields has empty values.

Actually it's impossible to use constraints with optional values.

For example:
this doesn't work if birth_date is not present

input UserInput {
  name: String @constraint(minLength: 2),
  surname: String @constraint(minLength: 2),
  dni: String,
  birth_date: String @constraint(format: "date")
}

And this would be awesome!

input UserInput {
  name: String @constra