<tbody>
                                                <c:forEach var="data" varStatus="s"
                                                           items="${webAuthenticationItems}">
                                                    <tr
                                                            data-href="${contextPath}/admin/webauth/details/4/${f:u(data.id)}">

///

## Написание шаблонов { #writing-templates }

Затем вы можете создать шаблон в `templates/item.html`, например:

```jinja hl_lines="7"
{!../../docs_src/templates/templates/item.html!}
```

### Значения контекста шаблона { #template-context-values }

В HTML, который содержит:

{% raw %}

```jinja
Item ID: {{ id }}
```

{% endraw %}

                                            <tbody>
                                            <c:forEach var="data" varStatus="s"
                                                       items="${badWordItems}">
                                                <tr
                                                        data-href="${contextPath}/admin/badword/details/4/${f:u(data.id)}">

                                            <tbody>
                                            <c:forEach var="data" varStatus="s"
                                                       items="${scheduledJobItems}">
                                                <tr
                                                        data-href="${contextPath}/admin/scheduler/details/4/${f:u(data.id)}" role="button" tabindex="0">

El objeto `app.webhooks` es en realidad solo un `APIRouter`, el mismo tipo que usarías al estructurar tu aplicación con múltiples archivos.

///

Nota que con los webhooks en realidad no estás declarando un *path* (como `/items/`), el texto que pasas allí es solo un **identificador** del webhook (el nombre del evento), por ejemplo en `@app.webhooks.post("new-subscription")`, el nombre del webhook es `new-subscription`.

/// info

The `app.webhooks` object is actually just an `APIRouter`, the same type you would use when structuring your app with multiple files.

///

Notice that with webhooks you are actually not declaring a *path* (like `/items/`), the text you pass there is just an **identifier** of the webhook (the name of the event), for example in `@app.webhooks.post("new-subscription")`, the webhook name is `new-subscription`.

///

```mermaid
graph TB

query_extractor(["query_extractor"])
query_or_cookie_extractor(["query_or_cookie_extractor"])

read_query["/items/"]

query_extractor --> query_or_cookie_extractor --> read_query
```

## Использование одной и той же зависимости несколько раз { #using-the-same-dependency-multiple-times }

                                            </thead>
                                            <tbody>
                                            <c:forEach var="artifact" varStatus="s" items="${installedArtifactItems}">
                                                <tr>
                                                    <td>${f:h(artifact.type)}</td>

                                            <tbody>
                                            <c:forEach var="data" varStatus="s"
                                                       items="${keyMatchItems}">
                                                <tr
                                                        data-href="${contextPath}/admin/keymatch/details/4/${f:u(data.id)}" role="button" tabindex="0">

                                            <tbody>
                                            <c:forEach var="data" varStatus="s"
                                                       items="${relatedContentItems}">
                                                <tr
                                                        data-href="${contextPath}/admin/relatedcontent/details/4/${f:u(data.id)}" role="button" tabindex="0">