This is a sibling issue to #5740. The same idea, but for entries in config files.
I envision the ability (via hooks?) to allow core and contrib modules/themes to specify names of deprecated config names/keys, and then map those to the respective new ones. If there is need to also manipulate the values for these keys, then perhaps also allow specifying functions that do that.
The idea is that if code calls config_get()/Config::get or config_set()/Config::set with a deprecated key name, then we automatically "redirect" these calls to read/save the new, replacement keys instead. We could also be logging "deprecated config entry called" messages, so that contrib can notice these and fix their code to not use the deprecated config key names in the first place.
This would help us in issues like #4569, where we have the need to rename a config key, but because that is also used in contrib-provided configuration files, we'd have to result in retaining the old name for backwards-compatibility reasons, even if the name and respective values would not make sense.
Recent comments
Hello. Welcome to Backdrop Some of the things you are asking for can be done with Ubercart. Ubercart out of the box supports buying a role, which could satisfy your paid memberships...
How to monetize a Backdrop site
Hi..., And welcome to our Backdrop community. Do you mean modules to help someone monetise their own website, or the official backdrop website?
How to monetize a Backdrop site
Title: Simplenews 1.x-1.2.2 removes subscribers when using anonymous checkout with Ubercart Hello, I experienced an issue when updating Simplenews to version 1.x-1.2.2. My site...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled