Move the field storage deletion if the last field has been removed to the UI layer

Created on 27 February 2015, over 10 years ago
Updated 3 June 2025, 5 days ago

Problem/Motivation

This issue is follow up of a suggestion given in Delete dependent config entities that don't implement onDependencyRemoval() when a config entity is deleted β†’ .
The main motivation is that API for deletion of field should not be responsible for deletion of the field storage. It should do only what the API method says that it will do and nothing more.

Proposed resolution

The code responsible to delete the field storage when the last field is deleted will be moved in the UI.

πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

field system

Created by

πŸ‡«πŸ‡·France boyan.borisov

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

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

  • πŸ‡«πŸ‡·France andypost

    the same time core (field ui) still has no UI to even know that there's any field's table and definitions exists...
    Moreover body field for node/comment is created automagically

  • πŸ‡«πŸ‡·France andypost

    Patch #15 is totally ok to convert to MR and add tests, it brings visibility at least

Production build 0.71.5 2024