From 9fe7029b53be6eb4ad6d13ecb40db89f419ba89e Mon Sep 17 00:00:00 2001 From: Alex Vandiver Date: Fri, 6 Oct 2023 18:05:10 +0000 Subject: [PATCH] docs: Remove an out-of-date TemplateView reference. No use of TemplateView passes a context anymore. --- docs/subsystems/html-css.md | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/docs/subsystems/html-css.md b/docs/subsystems/html-css.md index e5dfd484d0..7f94f81051 100644 --- a/docs/subsystems/html-css.md +++ b/docs/subsystems/html-css.md @@ -113,7 +113,7 @@ engine (files in `templates/zerver`). The syntax for using conditionals and other common structures can be found [here][jconditionals]. -The context for Jinja2 templates is assembled from a few places: +The context for Jinja2 templates is assembled from a couple places: - `zulip_default_context` in `zerver/context_processors.py`. This is the default context available to all Jinja2 templates. @@ -129,15 +129,6 @@ zerver/views/home.py: response = render(request, 'zerver/app/index.html', The next line in the code being the context definition. -- `zproject/urls.py` for some fairly static pages that are rendered - using `TemplateView`, for example: - -```python -path('config-error/google', TemplateView.as_view( - template_name='zerver/config_error.html',), - {'google_error': True},), -``` - ### Frontend templates For text generated in the frontend, live-rendering HTML from