use Jinja name consistently

This commit is contained in:
David Lord 2025-08-19 10:43:16 -07:00
parent 38b4c1e19b
commit d8259eb119
No known key found for this signature in database
GPG key ID: 43368A7AA8CC5926
9 changed files with 31 additions and 31 deletions

View file

@ -521,7 +521,7 @@ class App(Scaffold):
return os.path.join(prefix, "var", f"{self.name}-instance")
def create_global_jinja_loader(self) -> DispatchingJinjaLoader:
"""Creates the loader for the Jinja2 environment. Can be used to
"""Creates the loader for the Jinja environment. Can be used to
override just the loader and keeping the rest unchanged. It's
discouraged to override this function. Instead one should override
the :meth:`jinja_loader` function instead.

View file

@ -37,7 +37,7 @@ def _default_template_ctx_processor() -> dict[str, t.Any]:
class Environment(BaseEnvironment):
"""Works like a regular Jinja2 environment but has some additional
"""Works like a regular Jinja environment but has some additional
knowledge of how Flask's blueprint works so that it can prepend the
name of the blueprint to referenced templates if necessary.
"""