[TASK] Provide current template path in renderingContext#1337
Merged
Conversation
s2b
force-pushed
the
task/runtimeExceptions
branch
5 times, most recently
from
60b0725 to
e3e2878
Compare
s2b
changed the title
s2b
force-pushed
the
task/runtimeExceptions
branch
2 times, most recently
from
fb3f839 to
5de7aed
Compare
Previously, PHP code within the context of a template (most importantly ViewHelpers, but also internal Fluid code) wasn't aware of the current template context. This meant that exceptions couldn't refer to the template file where the exception was actually triggered. This change introduces the optional `originalTemplatePath` value both in the parser/compilation and in the rendering layer. When filled, it contains the full path to the template that is currently parsed or rendered. Since the value is also persisted to the cache, this path is even available for cached template files. In follow-up patches, this path can be used to improve exception messages within Fluid. It also allows users to access these values to improve exception messages in their own implementations.
s2b
force-pushed
the
task/runtimeExceptions
branch
from
5de7aed to
087be63
Compare
lolli42
approved these changes
Mar 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously, PHP code within the context of a template (most importantly
ViewHelpers, but also internal Fluid code) wasn't aware of the current
template context. This meant that exceptions couldn't refer to the
template file where the exception was actually triggered.
This change introduces the optional
originalTemplatePathvalue bothin the parser/compilation and in the rendering layer. When filled, it
contains the full path to the template that is currently parsed or
rendered. Since the value is also persisted to the cache, this path
is even available for cached template files.
In follow-up patches, this path can be used to improve exception
messages within Fluid. It also allows users to access these values to
improve exception messages in their own implementations.