- First commit to issue fork.
- @ericgsmith opened merge request.
- 🇳🇿New Zealand ericgsmith
Moved existing patch to MR.
I note that while this has been RTBC for almost 2 years there is mention in 📌 Refactor module architecture in a simpler, opinionated and more performant approach Needs review of removing views integration completely.
I have a use case that I am exploring using views to solve - and this patch gets me somewhat closer. Given this does a join from entity_usage to the entity its ignoring the vid - it would be good if we could either chose to join to the revision table instead of the base table, OR allow the relationship to have an additional config to add
'field' => $entity_type->getKey('revision'), 'left_field' => 'source_vid'to the
relationship.extra
definition in order to only relate based on the default revision.
I'm more curious about the future of the views integration for this module - are further patches welcome or is the future for views integration a different module?