Use toArray() instead of getValue() where applicable for field items and lists of field items

Created on 25 March 2014, about 11 years ago
Updated 13 May 2025, 5 days ago

Follow-up from #2223361: Rename ComplexDataInterface::getPropertyValues() to toArray(), remove setPropertyValues() β†’ .

We want to promote usage of toArray() over getValue() as we'll eventually rename or remove getValue() from those classes.

πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

field system

Created by

πŸ‡¨πŸ‡­Switzerland berdir Switzerland

Live updates comments and jobs are added and updated live.
  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

  • 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.

  • πŸ‡ΊπŸ‡Έ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!

  • πŸ‡¨πŸ‡­Switzerland berdir Switzerland

    getValue() is still a major DX issue, so I think this is still kind of valid, keeping of for now. Renaming getValue() is something I'd love to do, but I'm also aware about the impact that would have.

Production build 0.71.5 2024