-
benjamin melançon authored
Ultimately these should go the route of my every requirement in its own module, but.. we'll just live with it for now. Would be nice if Drupal had a facility for identifying *exactly* duplicate configuration, and being able to install a module without choking in that case. Then would be even nicer if it could identify substantially duplicate config (say, only 3rd party settings added) and leave the existing. Finally, it would be nicest to have a dialog to choose or merge configuration when enabling the module, and further that after you've enabeled the module and commit the configuration, Drupal is smart enough to know when it's enabling a module from configuration (following core.extension.yml) and not do this dialog because all the ultimately wanted config is already in config sync.
c5aed200