Didn't want to hijack the https://github.com/backdrop/backdrop-issues/issues/1855, because that one's been created for Documentation purpose, so am creating a new one.
Description of the need
As developers we find it always handy to set number of configurations in certain ways, for example, making it show all the errors on the screen, disabling some cache, or setting the current theme to rebuild its registry on every page load, etc. And instead of going through different pages on UI every time we start a new project, it's much easier just to use the feature discussed and introduced on https://github.com/backdrop/backdrop-issues/issues/1752.
Proposed solution
Nevertheless, the check for local settings file has already been introduced, manually compiling that kind of local settings file also takes valuable time. I suggest to take this further and add missing feature parity with Drupal 8 - as we can see on https://git.drupalcode.org/project/drupal/tree/8.8.x/sites Drupal 8 is shipped with the well-formatted example.settings.local.php file. It would be really useful for developers to have ready-to-use example.settings.local.php file in Backdrop core.
Recent comments
Those are nulls, and ive been checking every variable in both layout and block but there is nothing easy to edit. in layout: foreach ($variables['layout']->content as $key =...
How to hide block titles in certain regions
You could also do a similar thing in hook_preprocess_layout, just a slightly different order: get all the block ids from the positions you are interested in, then access those block objects to...
How to hide block titles in certain regions
when i check the classes, i found inside Layout class: /** * The main array of configured blocks, keyed by a generated ID per instance. * * @var Block[] */ var $content = array...
How to hide block titles in certain regions