} catch (Exception e) {
            fail("Failed to get field '" + name + "'", e);
            return null;
        }
    }

    /**
     * Test that the wire-format of the parameters is produced
     * correctly when all fields are set to typical values.
     */
    @Test
    void happyPathParameterEncoding() throws Exception {
        Configuration cfg = mock(Configuration.class);

///

## Combining information { #combining-information }

You can also combine response information from multiple places, including the `response_model`, `status_code`, and `responses` parameters.

You can declare a `response_model`, using the default status code `200` (or a custom one if you need), and then declare additional information for that same response in `responses`, directly in the OpenAPI schema.

          .isEqualTo(Strings.lenientFormat("", Arrays.copyOfRange(params, 2, params.length)));
    }
  }

  /**
   * Returns an array containing parameters for invoking a checkArgument, checkNotNull or checkState
   * method reflectively
   *
   * @param firstParam The first parameter
   * @param sig The method signature
   */
  @GwtIncompatible // ArbitraryInstances
  @J2ktIncompatible

          .isEqualTo(Strings.lenientFormat("", Arrays.copyOfRange(params, 2, params.length)));
    }
  }

  /**
   * Returns an array containing parameters for invoking a checkArgument, checkNotNull or checkState
   * method reflectively
   *
   * @param firstParam The first parameter
   * @param sig The method signature
   */
  @GwtIncompatible // ArbitraryInstances
  @J2ktIncompatible

///

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.

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

/// tip | Astuce

Certains éditeurs vérifient les paramètres de fonction non utilisés et les signalent comme des erreurs.

En utilisant ces `dependencies` dans le *décorateur de chemin d'accès*, vous pouvez vous assurer qu'elles sont exécutées tout en évitant des erreurs de l'éditeur/des outils.

Cela peut également éviter toute confusion pour les nouveaux développeurs qui voient un paramètre inutilisé dans votre code et pourraient penser qu'il est superflu.

    /**
     * Handles the help page request and renders the help interface.
     * This method performs authentication checks and sets up the necessary
     * form parameters and rendering data for the help page display.
     *
     * @return HtmlResponse containing the rendered help page or redirect to login if authentication is required
     */
    @Execute
    public HtmlResponse index() {

そして、次のような URL なら:

```
http://localhost:8000/items/?q=foo&q=bar
```

*path operation function* 内の *function parameter* `q` で、複数の `q` *query parameters'* 値（`foo` と `bar`）を Python の `list` として受け取ります。

そのため、このURLのレスポンスは以下のようになります:

```JSON
{
  "q": [
    "foo",
    "bar"
  ]
}
```

/// tip | 豆知識

## API Request Parameters

### WebIdentityToken