Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sub configuration as blocks in configuration files #5

Open
PhilippWendler opened this issue Dec 21, 2015 · 0 comments
Open

Sub configuration as blocks in configuration files #5

PhilippWendler opened this issue Dec 21, 2015 · 0 comments

Comments

@PhilippWendler
Copy link
Member

Sometimes, a configuration option refers to one or more further configuration options, e.g.,

sequential-analyses.configs = config1.properties, config2.properties

Sometimes, the exact config1.properties etc. does not fit, but needs some slight adjustments, i.e., some configuration values overwritten. This is only possible to handle by creating an extra file with #include config1.properties and the overwriting definitions.

As alternative, sub configurations like in the case above could be defined directly inside the main config file, like in this example:

sequential-analyses.configs = @config1, config2.properties

config1 {
  #include config1.properties
  overwritten-option = ...
}

This would be possible if the option sequential-analyses.configs is not defined as a list of file names, but as a list of Configuration instances, which could be created and injected directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant