This is basically the equivalent of https://www.drupal.org/project/drupal/issues/3163226 (as well as a sibling issue to #5741) which was introduced in D 9.1.x (Change record: Core settings keys can be deprecated)
If the
settings.phpfile for a site (or any file it includes) contains the legacy setting name, the deprecation warning will be generated. If code callsSettings::get('new_setting')but'new_setting'is not yet defined, the value of'old_setting'will be returned.If any code calls
Settings::get()with the legacy name, the deprecation warning will also be generated. If the replacement setting is already defined, the value returned bySettings::get('old_setting')will be the value ofnew_setting.
This would help us with issues similar to #4451 as well, and possibly allow us to deprecate things in the Backdrop 1.x release cycle instead of having to wait for 2.x.
Recent comments
Trying to push it to upstream 🤞 https://github.com/drush-ops/drush/pull/6621
Using Drush 8 with php 8
Wow, thank you!
Using Drush 8 with php 8
Hi folks, I went ahead and ported all drush 8.x stuff to PHP 8.3 and completely ripped out the legacy Symfony 2 internals. You can check out the exact details of what was done in the PR...
Using Drush 8 with php 8