Make it possible for custom viewsData class to adapt to entity schema changes.

Created on 23 February 2015, about 10 years ago

Updated 5 May 2025, 8 days ago

Problem/Motivation

The views data is coupled to the SQL schema. So once entity schema changes the views data change. We are automatically
adapting existing views, see #2341323: Adapt the references field / table names in views, when corresponding entity schema changes → but we have no clue yet how we adapt existing code in FooViewsData.

Here is a small excerpt of NodeViewsData which would break in case nodes are not translatable anymore:


    $data['node_field_data']['nid']['field']['id'] = 'node';
    $data['node_field_data']['nid']['field']['argument'] = [
      'id' => 'node_nid',
      'name field' => 'title',
      'numeric' => TRUE,
      'validate type' => 'nid',
    ];

Proposed resolution

Expose the following variables to be used $this->viewsBaseTable; $this->viewsRevisionBaseTable; $this->entityBaseTable

Remaining tasks

User interface changes

API changes

📌 Task

Status

Postponed: needs info

Version

11.0 🔥

Component

views.module

Created by

🇩🇪Germany dawehner

Live updates comments and jobs are added and updated live.

VDC
Related to the Views in Drupal Core initiative.

stale-issue-cleanup
To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 8 days ago →
🇺🇸United States smustgrave
Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024