ConfigEntityMapper::getBaseRouteParameters() should consult Entity::urlRouteParameters()

Created on 17 February 2016, about 9 years ago
Updated 17 March 2025, 17 days ago

Problem/Motivation

\Drupal\config_translation\ConfigFieldMapper::getBaseRouteParameters() duplicates the code in \Drupal\field\Entity\FieldConfig::urlRouteParameters() because it has no other choice, urlRouteParameters() is protected.
Any entity with a complex edit URL will have to do the same, and it will fatal error unless you do.

Proposed resolution

Rewrite \Drupal\config_translation\ConfigEntityMapper::getBaseRouteParameters() to consult \Drupal\Core\Entity\Entity::urlRouteParameters() once it (or something like it) is public.

Remaining tasks

N/A

User interface changes

N/A

API changes

N/A

Data model changes

N/A

πŸ› Bug report
Status

Active

Version

11.0 πŸ”₯

Component

content_translation.module

Created by

πŸ‡ΊπŸ‡ΈUnited States tim.plunkett Philadelphia

Live updates comments and jobs are added and updated live.
  • DrupalWTF

    Worse Than Failure. Approximates the unpleasant remark made by Drupal developers when they first encounter a particular (mis)feature.

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.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    This came up as the daily BSI target.

    Checking ConfigFieldMapper and FieldConfig I believe this is still true. Maybe it could be moved a trait? Thoughts?

Production build 0.71.5 2024