Right, now both the SqlContentEntityStorage and the schema handler have to work together based on a known table mapping, what makes the line between both object blurry.
- Make the SqlContentEntityStorage table mapping agnostic and get the table mapping from the schema handler
- As suggested by yched in we could create multiple table mapping classes for the different table mapping cases also.
- Agree on the exact way forward and do it.
User interface changes
None, only some base classes change a little