{
  "context": "This criteria evaluates how well the engineer uses Vuelidate's nested and complex object validation capabilities. The focus is on proper usage of validation rules for nested objects, arrays with per-item validation, and combining multiple validators appropriately.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Basic validator usage",
      "description": "Uses required, alphaNum, integer, and between validators correctly for top-level fields (username and age)",
      "max_score": 15
    },
    {
      "name": "Nested object validation",
      "description": "Correctly structures validation rules for nested objects (address.street, address.city, address.postalCode, contact.email, contact.phone) using dot notation or nested object structure",
      "max_score": 25
    },
    {
      "name": "String validators",
      "description": "Uses alpha validator for address.city, numeric validator for address.postalCode and phone fields, and minLength/maxLength validators appropriately",
      "max_score": 20
    },
    {
      "name": "Email validation",
      "description": "Uses the email validator from @vuelidate/validators for the contact.email field",
      "max_score": 10
    },
    {
      "name": "Array validation",
      "description": "Uses $each helper or equivalent to validate array items in emergencyContacts, applying validation rules to each array element",
      "max_score": 20
    },
    {
      "name": "Multiple validators",
      "description": "Combines multiple validators on single fields where required (e.g., postalCode needs both numeric and length validators, phone needs numeric and minLength)",
      "max_score": 10
    }
  ]
}