2018-11-08 16:14:14 +00:00
Starlette is not *strictly* coupled to any particular templating engine, but
Jinja2 provides an excellent choice.
2018-11-06 16:57:57 +00:00
2019-02-18 13:12:55 +00:00
Starlette provides a simple way to get `jinja2` configured. This is probably
what you want to use by default.
2018-11-06 16:57:57 +00:00
```python
from starlette.applications import Starlette
2019-11-13 12:25:18 +00:00
from starlette.routing import Route, Mount
2019-02-18 13:12:55 +00:00
from starlette.templating import Jinja2Templates
2019-06-17 02:28:04 +00:00
from starlette.staticfiles import StaticFiles
2018-11-06 16:57:57 +00:00
2019-02-18 13:12:55 +00:00
templates = Jinja2Templates(directory='templates')
2018-11-06 16:57:57 +00:00
async def homepage(request):
2019-02-18 13:12:55 +00:00
return templates.TemplateResponse('index.html', {'request': request})
2019-11-13 12:25:18 +00:00
routes = [
Route('/', endpoint=homepage),
Mount('/static', StaticFiles(directory='static'), name='static')
]
app = Starlette(debug=True, routes=routes)
2018-11-06 16:57:57 +00:00
```
2019-06-17 12:52:43 +00:00
Note that the incoming `request` instance must be included as part of the
2019-02-18 13:38:04 +00:00
template context.
2018-11-06 16:57:57 +00:00
2019-02-18 13:38:04 +00:00
The Jinja2 template context will automatically include a `url_for` function,
so we can correctly hyperlink to other pages within the application.
For example, we can link to static files from within our HTML templates:
2018-11-06 17:03:34 +00:00
```html
< link href = "{{ url_for('static', path='/css/bootstrap.min.css') }}" rel = "stylesheet" >
```
2019-12-10 14:58:44 +00:00
If you want to use [custom filters][jinja2], you will need to update the `env`
property of `Jinja2Templates` :
```python
from commonmark import commonmark
from starlette.templating import Jinja2Templates
def marked_filter(text):
return commonmark(text)
templates = Jinja2Templates(directory='templates')
templates.env.filters['marked'] = marked_filter
```
2019-02-18 13:12:55 +00:00
## Testing template responses
When using the test client, template responses include `.template` and `.context`
attributes.
```python
def test_homepage():
client = TestClient(app)
response = client.get("/")
assert response.status_code == 200
assert response.template.name == 'index.html'
assert "request" in response.context
```
2022-01-19 13:38:57 +00:00
## Customizing Jinja2 Environment
`Jinja2Templates` accepts all options supported by Jinja2 `Environment` .
This will allow more control over the `Enivornment` instance created by Starlette.
For the list of options available to `Environment` you can check Jinja2 documentation [here ](https://jinja.palletsprojects.com/en/3.0.x/api/#jinja2.Environment )
```python
from starlette.templating import Jinja2Templates
templates = Jinja2Templates(directory='templates', autoescape=False, auto_reload=True)
```
2018-11-06 16:57:57 +00:00
## Asynchronous template rendering
Jinja2 supports async template rendering, however as a general rule
we'd recommend that you keep your templates free from logic that invokes
database lookups, or other I/O operations.
2019-02-18 13:38:04 +00:00
Instead we'd recommend that you ensure that your endpoints perform all I/O,
2018-11-06 16:57:57 +00:00
for example, strictly evaluate any database queries within the view and
include the final results in the context.
2019-12-10 14:58:44 +00:00
[jinja2]: https://jinja.palletsprojects.com/en/2.10.x/api/?highlight=environment#writing-filters