TYPO3 v15 dev-main snapshot ()
This commit is contained in:
+31
@@ -0,0 +1,31 @@
|
||||
.. include:: /Includes.rst.txt
|
||||
|
||||
.. _feature-96961:
|
||||
|
||||
==============================================================
|
||||
Feature: #96961 - Backend routes contain Composer package name
|
||||
==============================================================
|
||||
|
||||
See :issue:`96961`
|
||||
|
||||
Description
|
||||
===========
|
||||
|
||||
Request objects in the backend already contain the resolved route
|
||||
object as attribute. These route objects now contain the Composer
|
||||
package name of the package ("extension") that defined the route as option:
|
||||
|
||||
.. code-block:: php
|
||||
|
||||
/** @var \TYPO3\CMS\Backend\Routing\Route $route */
|
||||
$route = $request->getAttribute('route');
|
||||
// Example return: "typo3/cms-backend" when EXT:backend defined that route.
|
||||
$packageName = $route->getOption('packageName');
|
||||
|
||||
Impact
|
||||
======
|
||||
|
||||
The package name can be useful for filesystem lookups
|
||||
or to bind configuration based on package name to it.
|
||||
|
||||
.. index:: Backend, PHP-API, ext:backend
|
||||
Reference in New Issue
Block a user