AliasManager should use the current route match for outbound alias pre-loading cache keys

Created on 18 June 2015, over 9 years ago
Updated 30 September 2024, 3 months ago

Problem/Motivation

AliasManager currently relies on PathSubscriber to set the cache key on the internal/system path after routing.

It could also just cache based on route + params, and we could lose that event subscriber entirely.

Proposed resolution

Inject the current route match. Make sure the cache key only gets set after routing has completed just in case.

Remaining tasks

User interface changes

None.

API changes

Removal of event listener, new dependency for AliasManager.

Data model changes

📌 Task
Status

Active

Version

11.0 🔥

Component

base system

Created by

🇬🇧United Kingdom catch

Live updates comments and jobs are added and updated live.
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.

Production build 0.71.5 2024