Move plugin manager classes out of \Type sub-namespace

Created on 4 December 2012, about 12 years ago
Updated 16 January 2025, 5 days ago

When the plugin system first went in, we converted aggregator.module as an example, and decided that the FetcherManager class should be in Drupal\aggregator\Plugin\FetcherManager, not Drupal\aggregator\Plugin\Type\FetcherManager.

Views currently has some manager classes in Drupal\views\Plugin\Type\, but in other issues, tim.plunkett indicated a willingness to move them up a level.

Field currently provides several supporting classes for formatters and widgets, and so provides a subnamespace for each: Drupal\field\Plugin\Type\Formatter\* and Drupal\field\Plugin\Type\Widget\*.

Do we want to standardize on whether to:
- always use Type,
- never use Type,
- or only use Type when wanting to have subnamespaces within it?

πŸ“Œ Task
Status

Postponed: needs info

Version

11.0 πŸ”₯

Component

plugin system

Created by

πŸ‡ΊπŸ‡ΈUnited States effulgentsia

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.

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

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for 8+ years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

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

    Only one manager remains in a Type directory: \Drupal\rest\Plugin\Type\ResourcePluginManager
    That class really shouldn't be in there, but unlike all the situations described in the original issue summary, there are no other classes in that directory.
    It *was* confusing when the manager was among the other classes, but that's not happening here.

    I think if anyone feels strongly now, they can open an issue to move ResourcePluginManager to a different directory, but this can be closed (and not just because it's stale).

Production build 0.71.5 2024