Child objects aren't processed by ValidationPipe

[ronniehicks]

I'm submitting a...

[ ] Regression 
[x ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

When providing a child to a @Body() parameter while using a global ValidationPipe the child object is not processed correctly and an "invalid" child object can make it through the validation pipe.

Expected behavior

Child objects will be inspected and blocked through the validation pipe

Minimal reproduction of the problem with instructions

Once you've cloned this repo post an invalid child object(s) to the POST /api/release endpoint.

What is the motivation / use case for changing the behavior?

This can't be correct behavior.

Environment

Nest version: 7.6.0

 
For Tooling issues:
- Node version: v14.16.1  
- Platform:  Mac/WSL 

Others:

VSCode 1.55.2
npm
Angular 11.2.10

[ronniehicks]

Oh, and as a follow up (let me know if you want me to create a different issue for this) if you attempt to hit an API endpoint that doesn't exist the calling client (Postman) doesn't get a 404 it just keeps trying

[kamilmysliwiec]

Can you share an example of an "invalid" object?

[ronniehicks]

{
  "name": "something",
  "track": {
    "name": "else"
  }
}

It's been awhile, but based on the example repo provided, that should be an invalid object (missing ordinal on track).