Issue Task Closed

#71279Allow use of TYPO3/Fluid without hacks

Claus Due 11/03/15, 14:40 updated 06/09/16, 12:23

Description

The only way to manipulate the composer autoloader
sufficiently to allow loading a package that replaces
a pseudo-package (e.g. typo3/cms-fluid) is to remove
the class loading entries provided by the TYPO3 core
via the root composer.json which cannot be replaced.
There are two ways of doing this:
1. Cumbersome composer installer scripts which are
against the nature of composer and considered hacks;
the script having to REWRITE a vital .php file.
2. A fast check in recorded PSR-4 prefixes in Bootstrap
to dynamically remove the prefix for the package that
is replaced; allowing the replacement prefix to remain
and become the active one.
Essentially this allows installing a “TYPO3 Fluid Adapter“
to replace the core Fluid extension. It does so ONLY
when detecting that the standalone Fluid package is
indeed present.

Reviews 1