Class-validator: ValidateNested without decorator is not working

[zender]

Let's say we have the following validation schema:

// this will not work
export const taskValidationSchema: ValidationSchema = {
  name: 'TaskValidationSchema',
  properties: {
    'title': [
      {
        type: 'minLength',
        constraints: [3],
        groups: ['admin'],
      }
    ],
    'files': [
      {
        type: 'nestedValidation',
        each: true,
        groups: ['admin'],
      }
    ]
  }
};

Validator is not aware of which validation schema to use for the nested property.

Here is my solution:

export const taskValidationSchema: ValidationSchema = {
  name: 'TaskValidationSchema',
  properties: {
    'title': [
      {
        type: 'minLength',
        constraints: [3],
        groups: ['admin'],
      }
    ],
    'files': [
      {
        type: 'nestedValidation',
        options: {'validationSchema': 'TaskFileValidationSchema'},
        each: true,
        groups: ['admin'],
      }
    ]
  }
};

Would you accept PR?

[enrico-calzavara]

@NoNameProvided any news on this?

[rlataguerra]

the decorator ValidateNested doesnt seems to work either

[NoNameProvided]

@rlataguerra please open a different issue for your issue explaining the details and providing a small example.

[henrikra]

@rlataguerra Are you experiencing the same as I with ValidateNested decorator? Can you also check @NoNameProvided and @19majkel94 Check this: https://github.com/typestack/class-validator/issues/281

[aviranhanan]

@NoNameProvided there is some estimation to fix this issue?

[joseym]

😞 so I guess this is still a problem with no fix on the roadmap...

I'm trying to dynamically generate a validation schema based on the results of an xhr request, and building a class isn't possible...

[NoNameProvided]

Marking this as blocked, as I want to start a discussion around the deprecation of the schema-based validation. I will CC the participants once I have created the issue.