Closed JadenKim-dev closed 2 months ago
Hi, @JadenKim-dev
As far as I know, there's no particular reason for this, it's simply missing.
The most likely reason is that my team doesn't use 'DotenvSourceProvider' and I didn't know about it. 😁
And as a background on providers, they expect you to create and utilize your own, not have it provided by config library.
A DotenvSourceProvider was created as a guide for creating providers.
Anyway, I'm not against adding it to inext.ts.
Can I look forward to your contribution?
Thank you for your kind explanation, @jiho-kr!
Considering your points, it would be beneficial to also export the abstract class AbstractConfigSourceProvider
to make it easier for users to implement their own provider.
I will proceed with this task and create a PR afterward! Thanks.
It has been resolved in https://github.com/woowabros/nestjs-library-config/pull/415.
Hi, there.
First of all, thanks for all your great works. This library resolved many inconveniences I experienced while using nest/config.
I wondered why source provider modules like
DotenvSourceProvider
are not exported in index.ts. It seems possible to specify the sourceProvider as an option in the ConfigModule.forFeature, but when I want to use DotenvSourceProvider, I can't import it.I want to use as below.
Current
index.ts
is like below. It exports only ConfigModule, AbstractConfigService, OptionalBoolean, ConfigScanner