ValidationSchema does not respect configuration provided to `load` about config

[kamilmysliwiec]

ValidationSchema is not intended to validate partial configurations #209 (comment)

You can put the validation logic directly in the factory.

[vtgn]

Hi!

I would like to reopen this issue because I got exactly the same problem.
Indeed, my "validate" function failed to validate the object built by the function given in the "load" field. By adding several console.log, I noticed the function given in the "load" field was called after the starting of the nest application, and so after the calling of the validate function.
I don't understand either why the files given in the "envFilePath" field are loaded before the calling of the "validate" method, and not the objects given in the "load" field.
This is totally illogical! And besides, the documentation says absolutely nothing on this subject.

When @kamilmysliwiec answered we can put the validation logic directly in the factory, we can also do the same with the files given in the "envFilePath", or with the environment variables of the system! This answer is just a nonsense, exactly the same way the "load" feature is implemented. Plus we must do two validations of the contents of ConfigService: absurd!
In that way, we don't need to use the ConfigModule and just manage our custom config object by ourselves. -_-°...

An API is made to facilitate the developers work, not to implement strange features that are completely illogical in certain cases with the goal of this API. The lack of information about this in the documentation and the several developers which don't understand why it doesn't work as expected prove the implementation of the "load" feature is illogical.

Regards.

[kamilmysliwiec]

Please search through some of our old issues on this (this has been discussed several times in the past).