Contrib.social

Enhance ConfigEntityBase::get() to support dot-delimited property names

Open on Drupal.org →
Created on 25 January 2013, over 12 years ago
Updated 23 June 2025, about 11 hours ago

Problem

  • Consuming code of more advanced config entities, typically with a $settings property, need a way to access sub-keys within $settings, without having to copy the entire $settings into a separate local variable first; i.e.:
    - $settings = $block->get('settings');
- $id = isset($settings['id']) ? $settings['id'] : NULL;
+ $id = $block->get('settings.id');

Proposed solution

  1. Import NestedArray in ConfigEntityBase.
  2. Change ConfigEntityBase::get() (+ set()) to support dot-delimited property names, retaining all other/original Entity::get() logic, and just performing the additional NestedArray::get() logic in the end:
      $value = ...;
  return NestedArray::get($value, explode('.', $name));
📌 Task
Status

Postponed: needs info

Version

11.0 🔥

Component

configuration entity system

Created by

🇩🇪Germany sun Karlsruhe

Live updates comments and jobs are added and updated live.
  • API clean-up

    Refactors an existing API or subsystem for consistency, performance, modularization, flexibility, third-party integration, etc. May imply an API change. Frequently used during the Code Slush phase of the release cycle.

  • stale-issue-cleanup

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

Sign in to follow issues

Comments & Activities

Not all content is available!

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

  • Comment about 11 hours 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