Review main Abandoned

85988[WIP][TASK] Use PathMap to handle published assets

Benni Mack CR 0 V -1 Hard +337 −119 updated 10/16/25, 19:22

Commit message

This change introduces as ResourcePathMap DTO,
which contains all paths that have a "published"
state within htdocs/_assets.

The main game changer here are that

a) The DTO ResourcePathMap is populated during composer-autoload
   time and cached, similar to PackageArtifact / PackageStates.php
   but NOT bound and completely detached from the PackageManager
   API.

b) The ResourcePublisher takes care of symlinking during composer-autoload
   time, where as the ResourceResolver can be used during
   TYPO3 runtime to find the real path to the file.

In addition, I'd like to actually do the following:
- Make use of the list of path mappings in the PathUtility
  to rewrite the paths there to only have ONE place where
  "_assets" is set / defined.
- Allow to create such an API for "reading" the paths
  also in non-composer mode to 100% rely on this API.
- Allow a package (such as EXT:contentblocks) to check
  all packages for additional paths via a PHP API (ServiceProvider?)

Review

  • Code review CR 0
  • Verified V -1
    • core-ci -1 CI

Files 7

Review log 34

  1. Benni Mack uploaded patch set 1 09/10/24, 17:54

  2. core-ci voted on patch set 1 V -1 09/10/24, 18:08 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/65304

  3. Benni Mack marked it work in progress 01/08/25, 16:28

  4. Benni Mack abandoned the change 10/16/25, 19:22