EntityViewsData::getViewsTableForEntityType() does the job of figuring out the database table that Views should use for a given entity type.
It's currently protected, but other modules need this logic too, when adding fields to views data in hook_views_data_alter().
For example, Flag module needs to add a relationship from entity types that have flags on them to the flagging entity. For this, it needs to know which base table Views uses for each entity type.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 2491687.3.drupal.getViewsTableForEntityType-public.patch | 1.66 KB | joachim |
| #1 | 2491687.drupal.getViewsTableForEntityType-public.patch | 1.5 KB | joachim |
Comments
Comment #1
joachim commentedComment #3
joachim commentedComment #4
dawehnerSeems sane
Comment #5
jibranFlag is widely used module including d.o. Having proper views support for it should be considered major task.
Comment #6
xjm@jibran, I don't think it's major, because the workaround is just to duplicate the one line of code where needed. However, agreed with task.
A part of my brain wanted to ask for a unit test for this since it's public now, but the other part of my brain said the method is trivial enough that meh. If someone else would like to file a followup to add test coverage, cool.
This is also missing a beta evaluation (really all non-critical tasks should always have one), but I think changes that make contrib code more reliable can also be prioritized, and it's not like there's any disruption. Going forward, though, please be sure to add beta evaluations to tasks during this phase of the release cycle.
Committed and pushed to 8.0.x. Thanks!