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

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

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

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

{% raw %}

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

{% endraw %}

...будет показан `id`, взятый из переданного вами «context» `dict`:

```Python
{"id": id}
```

                JvmVendor.OPENJDK.name.lowercase(),
                display = ParameterDisplay.PROMPT,
                description = "Java vendor to run the test with",
                options = JvmVendor.values().map { it.displayName to it.name.lowercase() },
            )
            text(
                testTaskOptionsParameterName,
                "",
                display = ParameterDisplay.PROMPT,

            boolean allowStubModel)
            throws ProjectBuildingException;

    // TODO this is only to provide a project for plugins that don't need a project to execute but need some
    // of the values from a MavenProject. Ideally this should be something internal and nothing outside Maven
    // would ever need this so it should not be exposed in a public API

and can be asserted as desired.

You can change/extend these stubs, and tests should not be breaking too much, since most tests
assert using expected values from the stubs. Normally, when you try to use data from the stubs that
have not been properly populated, you'll get a nullpointer in your test and you then have to
identify which stub creates that specific piece of data.

expiry:
  signingKeys: "3h"
  idTokens: "3h"

  # Options for controlling the logger.
  logger:
    level: "debug"
    format: "text" # can also be "json"

# Default values shown below
oauth2:
  # use ["code", "token", "id_token"] to enable implicit flow for web-only clients
  responseTypes: [ "code", "token", "id_token" ] # also allowed are "token" and "id_token"

        DomUtils.insertContentElement(customParent, "newChild", "new value");

        String xmlOutput = DomUtils.toXml(doc);

        // Should be appended at the end since no ordering is defined for customParent
        assertTrue(xmlOutput.contains("<newChild>new value</newChild>"), "Should contain new child element");

        int existingChildIndex = xmlOutput.indexOf("<existingChild>");

name: Regression
description: Report a problem about something that used to work
labels: [ "a:regression", "to-triage" ]
assignees: [ ]
body:
  - type: markdown
    attributes:
      value: |
        Please use our bug report template to report problems with something that has never worked.
        Regressions reports are greatly appreciated during our RC phase and before a final release.
  - type: textarea
    id: current-behavior
    attributes:

under the License. */ import org.apache.maven.plugin.AbstractMojo; /** * Does nothing. * * @goal java * @phase generate-sources * * @author Benjamin Bentmann */ public class AMojo extends AbstractMojo { /** @parameter expression="${version}" default-value="1.0" */ private String version; /** @parameter */ private String[] models; public void execute() { } } src/main/java/org/apache/maven/plugins/coreit/BMojo.java src/main/java/org/apache/maven/plugins/coreit/BMojo.java package org.apache.maven.plugin.coreit;...

    /**
     * Sets the user properties to use for interpolation and profile activation. The user properties have been
     * configured directly by the user on his discretion, e.g. via the {@code -Dkey=value} parameter on the command
     * line.
     *
     * @param userProperties The user properties, may be {@code null}.
     * @return This request, never {@code null}.
     */

Якщо Ви взаємодієте з цією операцією шляху, надсилаючи два HTTP-заголовки, наприклад:

```
X-Token: foo
X-Token: bar
```

Відповідь буде така:

```JSON
{
    "X-Token values": [
        "bar",
        "foo"
    ]
}
```

## Підсумок

Оголошуйте заголовки за допомогою `Header`, використовуючи той самий підхід, що й для `Query`, `Path` та `Cookie`.