We have an event feature split (stackable: TRUE; weight: 80) that adds a view for listing event nodes. We have a site split (stackable: TRUE; weight: 70) that overrides the behavior of the event split view by displaying it using FullCalendar. This means that the fullcalendar_views module is required for the site split, but not for the event split. When exporting, ideally what would happen is that Config Split would recognize that the event view exists in the event split and allow us to partially split it in the site split. However, because of the inclusion of fullcalendar_views in the modules list for the site split, all config that is determined to have that module as a dependency gets completely split regardless of what values we include in the complete split or partial split sections.
TBD
TBD
TBD
TBD
TBD
TBD
Active
2.0
Code
I'm also having a problem while trying to upgrade from Config Split 1.x to 2.x It seems similar to the current issue - being related to a module dependency in my split (the tmgmt module).
However, this issue seems to be related to how Config Split handles these indirect dependencies.
\Drupal\Core\Config\Entity\ConfigDependencyManager::getDependentEntities not only gets direct dependencies, but also gathers dependencies of those dependencies.