Metadata and options are now could be set in configuration files #862
It is useful to be able to have metadata and other options declared in configuration files (e.g.
This chage allows us to have something like this in our config files:
Currently every metadata and other options are supported (or I'd like to believe that). More examples in
If overall design and implementation is fine I could update the documentation.
Below are supported ways of value definition for various options.
I like this a lot. The implementation is well-factored and well-thought-out.
A few aspects I'll want to consider before acceptance:
Py3 failures seem to be connected with
I'll peep into
Yes, that's how it's currently done.
Yet I'm not sure whether it'll the right thing to do, since keys used there do not fully correspond with
So I propose that we skip unknown keys, and handle both forms for those clashing (it seems to be
What do you think?
There's one more thing I'm concerned with: it's seems that it'll the the right thing to expose even minimal API, so that automation tools could easily get already parsed and preprocessed data from configs without ado.