The JSON body structure can be seen from this sample:

<details><summary>Request Body Sample</summary>

```json
{
  "input": {
    "account": "minio",
    "groups": null,
    "action": "s3:ListBucket",
    "bucket": "test",
    "conditions": {
      "Authorization": [

        final Matcher matcher = pattern.matcher(value);
        while (matcher.find()) {
            final String key = matcher.group(2);
            String replacement = System.getProperty(key);
            if (replacement == null) {
                replacement = matcher.group(1);
            }
            matcher.appendReplacement(tunedText, replacement.replace("\\", "\\\\").replace("$", "\\$"));

        }

    int NT_STATUS_INVALID_COMPUTER_NAME = 0xC0000122;
    /** The pipe operation has failed because the other end of the pipe has been closed */
    int NT_STATUS_PIPE_BROKEN = 0xC000014b;
    /** The specified local group does not exist */
    int NT_STATUS_NO_SUCH_ALIAS = 0xC0000151;
    /** The user has not been granted the requested logon type at this computer */
    int NT_STATUS_LOGON_TYPE_NOT_GRANTED = 0xC000015b;

$(function() {
  $('input[type="text"],select,textarea', ".login-box,section.content")
    .first()
    .focus();
  $(".form-group .has-error")
    .first()
    .next("input,select,textarea")
    .focus();

  $("section.content input").keypress(function(e) {
    if (e.which === 13) {
      var $submitButton = $("input#submit, button#submit");
      if ($submitButton.size() > 0) {
        $submitButton[0].submit();
      }

package callbacks

import (
	"gorm.io/gorm"
)

var (
	createClauses = []string{"INSERT", "VALUES", "ON CONFLICT"}
	queryClauses  = []string{"SELECT", "FROM", "WHERE", "GROUP BY", "ORDER BY", "LIMIT", "FOR"}
	updateClauses = []string{"UPDATE", "SET", "WHERE"}
	deleteClauses = []string{"DELETE", "FROM", "WHERE"}
)

type Config struct {
	LastInsertIDReversed bool

   * RS, and US is least inclusive. (The content and length of a File, Group, Record, or Unit are
   * not specified.)
   *
   * @since 8.0
   */
  public static final byte FS = 28;

  /**
   * Group Separator: These four information separators may be used within data in optional fashion,

{% endfor %}
{% endif %}

{% endif %}

### Individual Sponsors

{% if github_sponsors %}
{% for group in github_sponsors.sponsors %}

<div class="user-list user-list-center">

{% for user in group %}
{% if user.login not in sponsors_badge.logins %}

                releasedVersionsFile()
            )
        }
    }
}

class LazyProjectVersion(private val version: Provider<String>) {
    override fun toString(): String = version.get()
}

group = "org.gradle"
version = LazyProjectVersion(gradleModule.identity.version.map { it.version })

/**
 * Returns the trimmed contents of the file at the given [path] after
 * marking the file as a build logic input.
 */

### 回傳值 { #return-values }

它們可以回傳值，也可以不回傳；無論如何，回傳值都不會被使用。

因此，你可以重複使用在其他地方已使用過的一般依賴（會回傳值），即使回傳值不會被使用，該依賴仍會被執行：

{* ../../docs_src/dependencies/tutorial006_an_py310.py hl[11,16] *}

## 一組路徑操作的依賴 { #dependencies-for-a-group-of-path-operations }

之後在閱讀如何組織較大的應用程式（[較大型應用程式——多個檔案](../../tutorial/bigger-applications.md)）時，你會學到如何為一組路徑操作宣告一個共同的 `dependencies` 參數。

## 全域依賴 { #global-dependencies }

# Modèles de paramètres d'en-tête { #header-parameter-models }

Si vous avez un groupe de **paramètres d'en-tête** liés, vous pouvez créer un **modèle Pydantic** pour les déclarer.

Cela vous permet de **réutiliser le modèle** à **plusieurs endroits** et aussi de déclarer des validations et des métadonnées pour tous les paramètres en une seule fois. 😎

/// note | Remarque

Cela est pris en charge depuis la version `0.115.0` de FastAPI. 🤓

///