Nest Configuration Files

Suggested new feature or improvement

I looked around the repo and in issues and didn't find an issue around this and since there aren't discussions figure this is the best place to ask.

For WinGet Configuration files, it would be nice if I could refer other winget configuration files easily. I could likely do a hack of creating a script that I execute referring to another winget config file and the winget configure command within another winget configure file, but I was wondering if there would be a more "native" approach that would require nested calls like this and make it feel more like a modular approach. I'm not sure exactly how the syntax would look, but it could also allow things winget configure validate and similar commands to provide better information natively of errors in nested configuration files and where they are located instead of the error being in the top level file or similar. Essentially it would import the modularized file into the place it is referenced in the parent file as if it was part of the top level file.

Scenario

When I am setting up configuration of my machine, I like the idea of being able to modularize setups into parts, that I can build up into full machine configurations. As an Ex: maybe across computers I want to set the same windows themes, but only on a computer I will develop on I will want to setup VS. If I can nest, I can create top level configurations that have these built-in choices of modules that make up the machine and I can pick and choose individual configurations if I want without it all being in one large file or having to refer to many files to get my configuration done.

Additional details

No response

microsoft / devhome