Automatically provide a changed field definition

Created on 4 March 2014, over 10 years ago
Updated 30 January 2023, over 1 year ago

Updated: Comment #0

Problem/Motivation

All entity types that implement EntityChangedInterface have implemented the method getChangedTime() in the exact same way. This duplication could be avoided by using a trait.

Proposed resolution

Provide an EntityChangedTrait that provides EntityChangedTrait::getChangedTime().

Because this method relies on the changed field of an entity, it makes sense for the trait to provide that field as well. Since there can only be one baseFieldDefinitions(), however, we cannot provide that directly in the trait. For this reason a private function changedFieldDefinitions() is introduced as part of the trait that entity types can call in their baseFieldDefinitions().

Remaining tasks

User interface changes

-

API changes

-

πŸ“Œ Task
Status

Needs work

Version

10.1 ✨

Component
EntityΒ  β†’

Last updated about 6 hours ago

Created by

πŸ‡©πŸ‡ͺGermany tstoeckler Essen, Germany

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.

  • The Needs Review Queue Bot β†’ tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

    Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

    Consult the Drupal Contributor Guide β†’ to find step-by-step guides for working with issues.

Production build 0.69.0 2024