Use request directly instead of handling a full request

Created on 7 March 2024, 10 months ago
Updated 6 September 2024, 4 months ago

The field ComputedBreadcrumbsItemList handles a second Request on line 49. This may lead to errors if the calculated field is called on Kernel destruct, because the session header has already been sent back to the client. Happens in several potential cases, e.g. Search API index immediately.

Would it be possible to create a route match directly from the Request created instead of going through a controller call?

🐛 Bug report
Status

Needs work

Version

1.2

Component

Code

Created by

🇨🇭Switzerland Siegrist

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024