Contrib.social

Implement `lookup_keys` in Component for optimized queries

Open on Drupal.org →
Created on 6 June 2025, 21 days ago

Overview

In 🐛 ContentCreatorVisibleXbConfigEntityAccessControlHandler's `view` access must refuse access to disabled config entities Active we found out that we could implement `lookup_keys` in Component for optimized queries.

However, the atypical default values for datetime and daterange prevented us to do it there.

Proposed resolution

  • Implement `status` in `lookup_keys` in Component for optimized queries.
  • This should ensure that the key_value store caches those components per status.
  • But as all-props components fails entity validation, the key_value store won't include the all-props component.
  • So we need to figure out how to handle the daterange and datetime default values.

User interface changes

None.

📌 Task
Status

Active

Version

0.0

Component

Config management

Created by

🇪🇸Spain penyaskito Seville 💃, Spain 🇪🇸, UTC+2 🇪🇺

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024