dcharkes / config Goto Github PK

Consider the following situation.

We have package:my_package with a CLI that invokes package:cc.
package:cc has a function compile(Config config).
package:my_package has a bin/build.dart that constructs a Config from the CLI invocation. It might use some config values itself, but it will also pass it to its invocation of compile.

package:my_package does not have to know about the configuration for package:cc but users of the package can still provide configuration. Some kind of dependency injection.

However, that leads to the question what if keys start conflicting.

Should we consider to make it best practise that every package only uses keys beginning with its own package name.

Kubernetes Helm can do overrides of not just strings from the command line.

See https://helm.sh/docs/intro/using_helm/