```

///

## Importe `Form` { #import-form }

Importe `Form` de `fastapi`:

{* ../../docs_src/request_forms/tutorial001_an_py39.py hl[3] *}

## Defina parâmetros de `Form` { #define-form-parameters }

Crie parâmetros de formulário da mesma forma que você faria para `Body` ou `Query`:

{* ../../docs_src/request_forms/tutorial001_an_py39.py hl[9] *}

* `@app.get()`
* `@app.post()`
* `@app.put()`
* `@app.delete()`
* etc.

{* ../../docs_src/response_status_code/tutorial001_py39.py hl[6] *}

/// note

          val message = record.message
          val parameters = record.parameters

          if (parameters != null && !message.startsWith("Raw") && !message.startsWith("Plaintext")) {
            if (verbose) {
              println(record.message)
              println(record.parameters[0])
            }

            // JSSE logs additional messages as parameters that are not referenced in the log message.

## Listen mit Typ-Parametern als Felder { #list-fields-with-type-parameter }

Aber Python erlaubt es, Listen mit inneren Typen, auch „Typ-Parameter“ genannt, zu deklarieren.

### Eine `list` mit einem Typ-Parameter deklarieren { #declare-a-list-with-a-type-parameter }

     * @throws IllegalAccessRuntimeException
     *             If the number of actual and formal parameters differ, if unwrapping of primitive arguments fails,
     *             or if after unwrapping, the parameter values cannot be converted to the corresponding formal parameter types,
     *             or if the constructor is related to an enum type
     * @see Constructor#newInstance(Object[])
     */

## Campos do tipo Lista com um parâmetro de tipo { #list-fields-with-type-parameter }

Mas o Python tem uma maneira específica de declarar listas com tipos internos ou "parâmetros de tipo":

### Declare uma `list` com um parâmetro de tipo { #declare-a-list-with-a-type-parameter }

Para declarar tipos que têm parâmetros de tipo (tipos internos), como `list`, `dict`, `tuple`,

  // Natural order

  /**
   * Returns a serializable ordering that uses the natural order of the values. The ordering throws
   * a {@link NullPointerException} when passed a null parameter.
   *
   * <p>The type specification is {@code <C extends Comparable>}, instead of the technically correct
   * {@code <C extends Comparable<? super C>>}, to support legacy types from before Java 5.
   *

/// tip

Some editors check for unused function parameters, and show them as errors.

Using these `dependencies` in the *path operation decorator* you can make sure they are executed while avoiding editor/tooling errors.

It might also help avoid confusion for new developers that see an unused parameter in your code and could think it's unnecessary.

///

/// info

 *      </td>
 *   </tr>
 *   <tr>
 *      <td>parameters</td>
 *      <td>N/A</td>
 *      <td>No</td>
 *      <td>Specifications for the parameters which this Mojo uses will be provided in <b>parameter</b> sub-elements
 *          in this section.
 *          <br>
 *          <i>NOTE: Parameters are discussed in more detail below.</i>
 *      </td>
 *   </tr>
 * </table>

    assert app.openapi()["paths"][path]["get"]["parameters"] == [
        {
            "required": True,
            "schema": {"title": expected_title, "type": "string"},
            "name": expected_name,
            "in": "path",
        }
    ]


@pytest.mark.parametrize(
    "path",
    [
        pytest.param("/required-str", id="required-str"),