feat: allow validate object literal (#1378)

[christian-forgacs]

Description

Add possibility to validate object literal with all decorators inclusive @ValidateNested. Base solution for this issue is from flisboac.

Checklist

• the pull request title describes what this PR does (not a vague title like Update index.md)
• the pull request targets the default branch of the repository (develop)
• the code follows the established code style of the repository
  • npm run prettier:check passes
  • npm run lint:check passes
• tests are added for the changes I made (if any source code was modified)
• documentation added or updated
• I have run the project locally and verified that there are no errors

Fixes

fixes #1378

[christian-forgacs]

@NoNameProvided sorry if I bother you about this. We need this feature for a project we are working on. Currently we are using a workaround which could be removed after merging the pull request and a release.

Do you already know when this pull request can be processed?

[scholz-timo]

We also require this feature for a project.

[scholz-timo]

@christian-forgacs can you create a temporary release from your fork?

[christian-forgacs]

@scholz-timo you can use my fork from GitHub. The only thing to do is to install it with this command, build it and move some folders:

npm install https://github.com/christian-forgacs/class-validator\#54dc1204fa5c04653ebcd1021d10db4eb243a4c1
cd node_modules/class-validator
npm install
npm run build:cjs && npm run build:es2015 && npm run build:esm5 && npm run build:types && npm run build:umd
mv build/* .
rm -r build node_modules

Now you use the fork in your project temporarily 😉

[sentientmachin3]

Oh I'd like this feature to be merged, looks promising to me