Contrib.social

Throw an exception when a widget doesn't return a field type's main value.

Open on Drupal.org →
Created on 28 March 2014, about 11 years ago
Updated 20 May 2025, 14 days ago

At #2226493: Apply formatters and widgets to Node base fields → , we lost hours trying to figure out why a new widget wouldn't work. It turned out that we were returning $element['value'] = array(…) (like most widgets do), while we should have been returning $element['target_id'] = array(…)… because an entity_reference item's main property is tarrget_id. This is extremely hard to debug. And a very simple mistake to make.

I talked to fago and we agreed that to improve DX, we should just throw an exception, so that the developer is immediately made aware upon trying the widget.

📌 Task
Status

Postponed: needs info

Version

11.0 🔥

Component

field system

Created by

🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺

Live updates comments and jobs are added and updated live.
  • 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 14 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