Remove deprecated usage of Migration::set() and Migration::getMigrationDependencies()

Created on 12 January 2023, almost 2 years ago
Updated 25 April 2024, 8 months ago

Problem/Motivation

This issue is a follow-up to πŸ“Œ [PP-1] Deprecate Migration::set() Postponed and πŸ“Œ $migration_dependencies has inconsistent structure Fixed . It should target the 11.0.x branch, which is not yet open.

Issue #279675 deprecated the method Drupal\migrate\Plugin\Migration::set(). Issue #3262395 deprecated calling Drupal\migrate\Plugin\Migration::getMigrationDependencies() without setting the optional $expand parameter set to TRUE.

When it is time to remove the deprecated method calls, there are some steps that are less obvious than for the usual deprecation. The purpose of this issue is to track those extra steps.

Proposed resolution

Enforce the strategy from #3262395: validate on set, expand on get. See that issue for an explanation.

  1. Remove code that expands dependencies when no longer needed.
  2. Remove code that validates the structure of the requirements array after it has been set.
  3. Remove the optional $expand parameter from getMigrationDependencies(). Always act as if it were set to TRUE.

Remaining tasks

User interface changes

None

API changes

Remove method calls that have already been deprecated.

Data model changes

None

Release notes snippet

N/A

πŸ“Œ Task
Status

Closed: duplicate

Version

11.0 πŸ”₯

Component
MigrationΒ  β†’

Last updated about 13 hours ago

Created by

πŸ‡ΊπŸ‡ΈUnited States benjifisher Boston area

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