e.g. isPassportNumber, etc.

We need to update our README.md file before the 1.0 release.

• [ Y] Are you running the latest version?
• [ Y] Have you included sample input, output, error, and expected output?
• [ Y] Have you checked if you are using correct configuration?
• [ N] Did you try online tool?

Description

When a json includes a number, and running the code example appearing in fast-xml-parser site, causes

default

const V = require('fastest-validator');

const v = new V();

const schema = {
  tuple: {
    type: 'tuple',
    empty: false,
    items: [{ type: 'string', default: '1' }],
  },
};

const data = { tuple: [] };
console.log(v.validate(data, schema));
console.log(data);

[
  {
    type: 'tupleEmpty',
    message: "The 'tuple' field must not be an empty

• 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

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