Config: mechanism for changes in parameters
Follow-up of #87 (closed).
Future-proofing for supporting different versions should be implemented in nabu.io.config.validate_nabu_config
.
Each section/key can be tested individually, and possibly re-mapped with a "options names mapping", eg.
deprecation_mapping = {
"phase": {
"paganin_delta_beta": { # the parameter named changed for something else
"new_name": "delta_beta",
"from_version": 2020.3,
"compatible_versions": [2020.3, 2020.4], # range of nabu versions compatible with the old name
}
}
Edited by Pierre Paleo