Centralize extension name length validation into ExtensionDiscovery

Created on 18 April 2014, over 11 years ago
Updated 22 September 2025, 29 days ago

Problem

  1. Various code spots throughout core are validating the length of extension names, whereas...

  2. An extension with a too long name MUST NOT enter the application in the first place.

Proposed solution

  1. Centralize extension name length validation into ExtensionDiscovery.

📌 Task
Status

Postponed: needs info

Version

11.0 🔥

Component

extension system

Created by

🇩🇪Germany sun Karlsruhe

Live updates comments and jobs are added and updated live.
  • API clean-up

    Refactors an existing API or subsystem for consistency, performance, modularization, flexibility, third-party integration, etc. May imply an API change. Frequently used during the Code Slush phase of the release cycle.

  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

  • Needs change record

    A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.

  • stale-issue-cleanup

    To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

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.

No activities found.

Production build 0.71.5 2024