FieldItem::isEmpty() should rely on $property->isRequired()

Created on 3 January 2015, over 10 years ago

Updated 24 April 2025, 2 days ago

Now that #2232477: Fatal when adding new fields with NOT NULL constraints in a base table that contains existing entities → leveraged the concpet of isRequired() on FieldItems' properties, this is what the base implementation of FieldItem::isEmpty() should rely on :
By default, an item is considered empty if any of its required properties is NULL.

Hopefully this should also let us remove a couple custom isEmpty() implementations in some field types.

📌 Task

Status

Postponed: needs info

Version

11.0 🔥

Component

field system

Created by

🇫🇷France yched

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

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 2 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!
Comment 2 days ago →
🇷🇴Romania amateescu
This is still relevant and not implemented yet :)

Production build 0.71.5 2024