Support for nested configs

[yugal-dream11]

Current config creation

• Declare all configuration properties at one root level folder defaulting to config
• Builds one config for the application with one type definition

Issues with current approach

• Does not support modularised config maintenance
• Resulting in cluttered config which becomes difficult to reason about.

Proposed extension for nested configs

• Ability to have module/folder level config
• Explicit type definition for nested configs
• Explicit config creation for nested configs
• Import configs relatively

Expected support

• Supports annotated variable replacements
• Expects default.json to be present at nested config levels
• Generates corrects typings and config json

Example

Input folder structure

├── config
│   ├── default.json
│   ├── deployment
│   │   └── www.example.com.json
│   ├── env
│   │   └── production.json
│   └── user
│       └── root.json
└── module-1
    └── config
        ├── default.json
        ├── deployment
        │   └── www.example.com.json
        ├── env
        │   └── production.json
        └── user
            └── root.json

Resulting config creation

├── config
│   ├── default.json
│   ├── deployment
│   │   └── www.example.com.json
│   ├── env
│   │   └── production.json
│   ├── index.d.ts
│   ├── index.js
│   └── user
│       └── root.json
└── module-1
    └── config
        ├── default.json
        ├── deployment
        │   └── www.example.com.json
        ├── env
        │   └── production.json
        ├── index.d.ts
        ├── index.js
        └── user
            └── root.json