See \Drupal\Tests\experience_builder\Functional\ContentTemplateDependencyTest::testRemoveFieldTypeProviderModule().
The same automatic updating is needed for Pattern and PageRegion config entities (aka all other XB config entity types that implement ComponentTreeEntityInterface).
::onDependencyRemoval() for Pattern and PageRegionComponentTreeItem::updatePropSourcesOnDependencyRemoval() to achieve that, see \Drupal\experience_builder\Entity\ContentTemplate::onDependencyRemoval() for how to do thatContentTemplateDependencyTest::testRemoveFieldTypeProviderModule(), but as a kernel test rather than a functional test. Add \Drupal\Tests\experience_builder\Kernel\Config\PatternTest and …\PageRegionTest.::onDependencyRemoval() implementations to move that logic into a trait to share the logicWhen uninstalling a module providing a field type in use by Patterns or PageRegions, those Patterns or PageRegions would no longer be listed to get uninstalled! 👍 😅
Note that this is far less likely to occur, hence marking this for a later phase.
I don't think this is either a beta or a stable blocker. 👍 We could potentially remove later phase in case someone wants to contribute to this since it would be a nice UX/DX improvement.
Alright, unpostponing, but reflecting the lower urgency for this by reducing priority to .
Thanks, @lauriii!