Use parent method for when not preserving

Created on 8 June 2022, over 2 years ago
Updated 3 January 2024, 9 months ago

Problem/Motivation

The current method specifically does not call the parent method due to deprecations in core; however, this causes the module to become out of date whenever the core parent has implementation changes. I think the better method here is to utilize the parent and work around such core issues until they are resolved.

Steps to reproduce

My example was I am using a patch for core that has yet to be merged that fixes migrations by changing the parent method, but I also use this module so that patch was never being hit due to the above.

Proposed resolution


- Work around core deprecations for tests until core is updated.

Feature request
Status

Needs work

Version

2.0

Component

Code

Created by

🇨🇦Canada b_sharpe

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

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