Features add a globals per template rendering ( e.g. per http request) #50
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.
At the moment, while rendering an HTTP request, we can't have globals variable per request.
While rendering templates in framework such as FastAPI, or pyramid, there is a request
object that can be passed to the rendering engine in order to get some request
context, it can render url or access to the current session.
While rendering a template, in classic Jinja2, we can set them while fetching the template,
in a get_template call
for example.
Using JinjaX, I propose that we can pass them with a
__globals
as we can have other__params
already.I am not sur that the implementation is thread safe but if it works for css or js, it could works for those variable.