Suggestion

Enable glob-based paths for ConfigSchemas in the .configu file and with the --schema flag on the CLI. When a glob path is used, the interface will expand it, and if multiple schemas are found, it will combine them. If a key is in multiple schemas, the "deepest" one takes precedence.

Motivation

Simplifies managing multiple schemas by allowing pattern-based file selection. Useful for projects with hierarchical or scattered configurations. Ensures specific configurations override general ones.

Context

Currently, users must specify each schema file individually, which can be cumbersome and error-prone, especially in large projects with many configuration files. By allowing glob-based paths, we streamline the process, making it easier to manage and apply multiple schemas. This is particularly useful in environments where schemas are organized in a directory structure that reflects their scope and specificity.

For instance, a user might have a directory structure where common schemas are in a top-level directory, and more specific schemas are nested deeper. By using a glob pattern, such as schemas/**/*.yaml, the interface will automatically include all relevant schemas. If a key is declared in multiple schemas, the rule that the "deepest" one wins ensures that the most specific configuration is applied.