## Beispiel { #example }

Hier ist ein Beispiel für eine *Pfadoperation* mit Parametern, die einige der oben genannten Typen verwenden.

{* ../../docs_src/extra_data_types/tutorial001_an_py310.py hl[1,3,12:16] *}

Beachten Sie, dass die Parameter innerhalb der Funktion ihren natürlichen Datentyp haben und Sie beispielsweise normale Datumsmanipulationen durchführen können, wie zum Beispiel:

 * <code>java.io.File</code> usage; a '/' at the beginning of the second
 * parameter will still use the server component of the first parameter. The
 * examples below illustrate the resulting URLs when this second contructor
 * argument is used.
 *
 * <table border="1">
 * <caption>Examples Of SMB URLs When Augmented With A Second Constructor Parameter</caption>
 * <tr>
 * <td colspan="3">

        this.connectionBuilder = connectionBuilder;
        return this;
    }

    /**
     * Adds a request parameter.
     *
     * @param key the parameter key
     * @param value the parameter value
     * @return this CurlRequest instance
     */
    public CurlRequest param(final String key, final String value) {
        if (value == null) {

labels.boost=Boost
labels.crawlingConfigName=Name
labels.crawlingConfigPath=Path to Crawl
labels.processType=Process Type
labels.parameters=Parameters
labels.designFile=File to Upload
labels.bulkFile=Bulk File
labels.appendQueryParameter=Append Search Parameters
labels.configId=Config ID
labels.configParameter=Config Parameter
labels.content=Content
labels.csvFileEncoding=CSV Encoding
labels.defaultLabelValue=Default Label

// decreasing precedence:
//
// 1. the value of the corresponding environment variable if set,
// 2. the value of the parameter in the config store if set,
// 3. the default value,
//
// This function only works for a subset of sub-systems, others return
// `ValueSourceAbsent`. FIXME: some parameters have custom environment
// variables for which support needs to be added.
//

Dies erfolgt nicht innerhalb jedes in OpenAPI enthaltenen JSON-Schemas, sondern außerhalb, in der *Pfadoperation*.

### Verwendung des Parameters `openapi_examples` { #using-the-openapi-examples-parameter }

Sie können die OpenAPI-spezifischen `examples` in FastAPI mit dem Parameter `openapi_examples` deklarieren, für:

* `Path()`
* `Query()`
* `Header()`
* `Cookie()`
* `Body()`
* `Form()`
* `File()`

        assertTrue(transaction.hasMoreElements());
    }

    @Test
    @DisplayName("Test reset with key and lastName")
    void testResetWithKeyAndLastName() {
        // Reset with parameters should not throw exception
        assertDoesNotThrow(() -> transaction.reset(123, "testName"));

        // Transaction should be ready for reuse
        assertTrue(transaction.hasMoreElements());
    }

To return a response with HTML directly from **FastAPI**, use `HTMLResponse`.

* Import `HTMLResponse`.
* Pass `HTMLResponse` as the parameter `response_class` of your *path operation decorator*.

{* ../../docs_src/custom_response/tutorial002_py39.py hl[2,7] *}

/// info

The parameter `response_class` will also be used to define the "media type" of the response.

In this case, the HTTP header `Content-Type` will be set to `text/html`.

        if (mojoDescriptor.getParameters() != null) {
            for (Parameter parameter : mojoDescriptor.getParameters()) {
                XmlNode parameterConfiguration = executionConfiguration.child(parameter.getName());

                if (parameterConfiguration == null) {
                    parameterConfiguration = executionConfiguration.child(parameter.getAlias());
                }

///

It has all the information about the *path operation* and is used to generate the automatic documentation.

It includes the `tags`, `parameters`, `requestBody`, `responses`, etc.

This *path operation*-specific OpenAPI schema is normally generated automatically by **FastAPI**, but you can also extend it.

/// tip

This is a low level extension point.