Child Entity v2 - ChildEntityTrait

I have created a new version of Child Entity using a trait rather than a base class.
This follows the same pattern as the core EntityChangedTrait and EntityPublishedTrait.

I am happy to become a maintainer of the module for the v2 branch.

There will be no upgrade path from v1 to v2 as users will need to update their code.

This makes the use of Child Entity more flexible and I hope creates a path to Drupal 9.

https://github.com/committeehq/child_entity

Checklist

  • Link to project: Child Entity
  • Record of owner agreement: No.
  • Maintainers: JSON
  • Year of last Drupal.org activity of maintainer: lostcoder 2019
  • Record of attempts to PM owner and maintainers: No Contact form
  • Project covered by Drupal’s security advisory policy: No

Comments

dwkitchen created an issue. See original summary.

dwkitchen’s picture

Title: v2 ChildEntityTrait » Offering to maintain ChildEntityTrait to add 2.0 version
Category: Feature request » Support request
dwkitchen’s picture

Project: Child Entity » Drupal.org project ownership
Version: 8.x-1.1 »
Component: Code » Maintaining offer

The project owner has disabled the contact form on their profile so I have been unable to contact them.

dwkitchen’s picture

Title: Offering to maintain ChildEntityTrait to add 2.0 version » Offering to maintain Child Entity to add 2.0 version
avpaderno’s picture

Title: Offering to maintain Child Entity to add 2.0 version » Offering to maintain Child Entity
Category: Support request » Task
gisle’s picture

Assigned: Unassigned » gisle
Issue summary: View changes
Status: Active » Fixed

dwkitchen,
thank you for offering to create and maintain ver. 2 of project as a trait and to carry it forward to Drupal 9.

As the owner cannot be contacted, and that the present owner can continue maintaining ver. 1 if he/she still wants to, I am going to add you as maintainer. The alternative would be to fork it, fragmenting our namespace.

gisle’s picture

Issue summary: View changes

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.