Use base fields instead of configurable fields

Created on 21 July 2021, over 3 years ago
Updated 8 February 2024, about 1 year ago

Problem/Motivation

The easy email offers nice functionality but at a cost. Every email type you add to your site causes an explosion of configurable fields to manage. I have a site with 28 email types and this results in 406 field.field.easy_email.* fields! This results in extra tables and extra work and I'm not sure why. As far as I can see all of these things should be base fields on the \Drupal\easy_email\Entity\EasyEmail entity type. I can't see why there is an advantage in allowing a user to remove them. It creates code complexity and we don't have to default them to required.

Proposed resolution

Move all of this to base fields and provide an update path.

Remaining tasks

User interface changes

API changes

Data model changes

πŸ“Œ Task
Status

Fixed

Version

3.0

Component

Code

Created by

πŸ‡¬πŸ‡§United Kingdom alexpott πŸ‡ͺπŸ‡ΊπŸŒ

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

Production build 0.71.5 2024