You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The question is if this is a bug or not. The documentation states:
During processing, the following variables are available in the template:
Default Jinja or ESH Description
------------- ------------- ----------------------------
...
yadm.source YADM_SOURCE Template filename
Guess it boils down to if the "template" is the original template file or any included file. For the default template processor it would be possible to update yadm.source when including files, but for the others it wouldn't work. So I'm leaning towards the current behavior being the correct. But I'm interesting to hear if you have some other view on it?
I definitely have another view, because when you get over 2 templates deep it becomes more challenging to find out where code came from in the final result. also if you're using SPDX snippets you might have a licenses that is different from aggregated file. I guess I kind of expect it to work similar to a location in a logger, printing the correct class/file; without the line number in this case.
I speculate that the description and variable name don't really match, and since a template can include a template, although it doesn't have to be a template that's included.
Describe the bug
if doing multiple nested includes the
{{ yadm.source }}
will be incorrect past the first levelTo reproduce
in our os file
in the vim file
OUTPUT
Expected behavior
note: I put nothing between the
.
and the,
because it would be an empty string if no class is setEnvironment
Additional context
[Add any other context about the problem here.]
The text was updated successfully, but these errors were encountered: