Each entity that makes use of Field Inheritance generates a new entry in the key_value database table.
However, there's no control to cleanup that table which might grow more than necessary given that modules does not control when entries must be removed from the storage.
Module should provide a garbage collector service to cleanup the data when entities are removed or the module is uninstalled.
Install a Vanilla Drupal site with Field Inheritance module
Create one or more Field Inheritance entities
Create several content entities as destination of those Field Inheritances
Confirm that each entity generates an entry in the key_value DB table in the field_inheritance collection
Delete part of those entities
Confirm that entries related to those entities are not removed from the DB
Uninstall the field_inheritance module
Confirm that any of the module related DB entries are removed from the DB
Active
3.0
Code
Postponing on 📌 Store relation with the parent entity in the database instead of the State API Active . We might not need this one if the other goes in.
After 📌 Store relation with the parent entity in the database instead of the State API Active this is not necessary anymore. The Field Inheritance information is stored at entity level and the upstream Drupal subsystems take care of it.