>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3518869. --> Reported by: [ergonlogic](https://www.drupal.org/user/368613) Related to !33 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>I often forget to enforce relevant configs, since you explicitly have to flag them for enforcement. For example, when I add a new field, I might remember to enforce the field storage and instance settings, but to enforce form and view display settings.</p> <p>It'd be nice to be able to automatically enforce all configs from any config forms that I've saved.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>We could add a global setting to enforce configs by default. That way, when we interact with any new config form, the "enforce config" checkbox will be checked, and we won't have to remember to do so. Once we've worked out the kinks, I'd even suggest making that the default behaviour (maybe in v2).</p> <p>One challenge here is that we assume that any config that is not stored in a target module registry is not enforced. When we load the config enforce form, how would we be able to differentiate between (a) not having yet interacted with this config, versus (b) having disabled enforcement for it? It doesn't even make sense to store such data in a target module registry (ie. which registry should be responsible for <em>not</em> enforcing the foo.bar config?)</p> <p>I think the solution lies in leveraging our "unenforced configs" setting. When handling the submission of a config enforce form, if (and only if) we're enforcing by default, we can add the related config to <code>config_enforce_devel.settings.ignored_configs</code>. This setting currently has no effect on the CED form itself. However, when building the form (and we're enforcing by default), we could uncheck the "enforce" checkbox (and update its label to indicate the config is currently being ignored), if the related config is in <code>ignored_configs</code>.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li><del>Address TODOs in code</del> Done!</li> <li>Consider (here or in a follow-up) prompting the user to enforce Config Enforce Devel settings, because the ignored list is only stored in Config Enforce Devel settings, and won't be persisted unless that config is enforced.<br>Created <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/config_enforce_devel/issues/3558885" title="Status: Active">#3558885: Prompt user to enforce CED settings into a target module</a></span> and this can be handled there or in a follow-up.</li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <p>Changes to Config Enforce Devel settings form:</p> <ul> <li>Reorders the Config Enforce Devel settings form to bring "Enforcement defaults" (was "Enforcement field defaults") to the top.</li> <li>Adds a new checkbox in the "Enforcement defaults" section to "Enforce all config objects by default" (defaults to TRUE)</li> <li>Initially opens the details elements on the Config Enforce Devel settings form</li> <li>Re-labels "Unenforced configs" to "Ignored configs"</li> </ul> <p>Changes to single Config Enforce forms:</p> <ul> <li>Enforce config is checked by default, unless the config is ignored in Config Enforce Devel settings</li> <li>Labels and descriptions are updated to explain the workflow when using Enforce by default</li> </ul> <p>Screenshots follow, but note they are slightly outdated in some aspects.</p> <h4>Before</h4> <p><img src="https://www.drupal.org/files/issues/2025-05-01/config_enforce_devel-3518869-6-before.png" alt="Config Enforce Devel settings form before changes"></p> <h4>After</h4> <p><img src="https://www.drupal.org/files/issues/2025-05-01/config_enforce_devel-3518869-6-after.png" alt="Config Enforce Devel settings form after changes"></p> <h3 id="summary-api-changes">API changes</h3> <p>Should be none.</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>Config changes only:</p> <ul> <li>Adds a new config key config_enforce_devel.settings.defaults.enforce_by_default</li> <li>Adds config schema for missing elements within config_enforce_devel.settings</li> </ul> > Related issue: [Issue #3341143](https://www.drupal.org/node/3341143)