`drush theme:dev on` changes aggregation in a way that is exportable to YAML config

[bserem]

Up until now we relied on settings overriddes to disable aggregation locally:

annertech-ddev/settings.local.devmode.php

Line 76 in 8bc95a1

$config['system.performance']['css']['preprocess'] = FALSE;

Lately we switched to the new drush theme:dev on command (drush 13.6+) with the idea that we move away from custom overrides towards a community driven approach.

annertech-ddev/commands/host/devmode

Line 23 in 8bc95a1

if [[ $DRUSH_IS_COMPATIBLE = true ]]; then ddev exec drush theme:dev off; fi

Since then we are experiencing a lot of commits where disabling aggregation has sneaked in config changes, something we must avoid.

I strongly suspect the switch to drush is the issue here, as it changes the values in Drupal and doesn't override them.

We need to consider if we revert to custom overrides or if we strengthen our pre-commit and pre-push hooks to avoid this reaching production sites.

[bserem]

Verified that drush is the cause here.

Switch to using a customized development.services.yml OR drush commands to set twig debugging. Leave css/js aggregation as an overridden setting in settings.local.php
Resources:

• https://www.drupal.org/docs/develop/theming-drupal/twig-in-drupal/debugging-twig-templates#s-enable-twig-debug-mode
• https://git.drupalcode.org/project/drupal/-/blob/11.x/sites/development.services.yml
• https://drupal.stackexchange.com/questions/316808/struggling-to-enable-twig-debugging with keyVal setting (probably easiest and preferred)