Hesoyam

@toonvanstrijp I believe when we're using a translation library, we aim to avoid confusion and keep the error messages as simple as possible so that the front-end application can print...

Don't you think it's tedious to follow that nested translation syntax for hundreds of properties? @toonvanstrijp Wouldn't it be better to have a feature internally to map properties against `validation-properties.json`...

@toonvanstrijp I'd like to, but I'm not super familiar with this library's structure. Would you mind suggesting from which part I need to start? Or where can I implement this...

> @kamilmysliwiec Is this targeted for some version of Nest? What do you think of the two solutions/workarounds ([#1](https://github.com/nestjs/nest/issues/2343#issue-452615228) [#2](https://github.com/nestjs/nest/issues/2343#issuecomment-678937523))? Do they have any downsides? E.g. #1 would create everything...

This is how I added this feature to my application by using the [env-var](https://www.npmjs.com/package/env-var) package. https://gist.github.com/Scrip7/63a159057e733284fdc963f3f2d2acdc `transport-config.ts`: ```TypeScript import { NestMicroserviceOptions } from '@nestjs/common/interfaces/microservices/nest-microservice-options.interface'; import { MicroserviceOptions, RedisOptions, RmqOptions, TcpOptions,...