Project

General

Profile

Actions
Copy link

Task #90218

closed

Dissolve PersistenceDelegate for persisted mappers

Added by Oliver Hader almost 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Site Handling, Site Sets & Routing
Target version:
-
Start date:
2020-01-27
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

The intention of PersistenceDelegate was to provide a generic API to
resolve or generate route components. However the implementation did
not provide any additional behavior. It just was used as structural
pattern which did not provide any further advantages.

That's the reason why PersistenceDelegate gets dissolved and its
database connection invocation is moved to its corresponding callers
PersistedAliasMapper and PersistedPatternMapper.

Related issues 3 (1 open — 2 closed)

Related to TYPO3 Core - Bug #89153: Wrong Extbase record is shown for slugClosed2019-09-11

Actions
Related to TYPO3 Core - Bug #90269: Use correct method name in PersistedPatternMapper legacy traitClosed2020-01-31

Actions
Related to TYPO3 Core - Bug #92368: PersistedAliasMapper: 404 error when linking to a non-translated news recordNew2020-09-22

Actions
Actions
Copy link

Also available in: Atom PDF