Hidden: true,
	},
}

// Help template for minio.
var minioHelpTemplate = `NAME:
  {{.Name}} - {{.Usage}}

DESCRIPTION:
  {{.Description}}

USAGE:
  {{.HelpName}} {{if .VisibleFlags}}[FLAGS] {{end}}COMMAND{{if .VisibleFlags}}{{end}} [ARGS...]

COMMANDS:
  {{range .VisibleCommands}}{{join .Names ", "}}{{ "\t" }}{{.Usage}}

```Python hl_lines="3  5"
{
    "name": "Bar",
    "description": "The bartenders",
    "price": 62,
    "tax": 20.2
}
```

응답에 포함됩니다.

#### 기본값과 동일한 값을 갖는 데이터 { #data-with-the-same-values-as-the-defaults }

데이터가 ID가 `baz`인 항목처럼 기본값과 동일한 값을 갖는다면:

```Python hl_lines="3  5-6"
{
    "name": "Baz",
    "description": None,
    "price": 50.2,
    "tax": 10.5,
    "tags": []
}

리스트는 각 태그에 대해 하나의 딕셔너리를 포함합니다.

각 딕셔너리에는 다음이 포함될 수 있습니다:

* `name` (**필수**): *경로 처리* 및 `APIRouter`의 `tags` 매개변수에서 사용하는 태그 이름과 동일한 `str`입니다.
* `description`: 태그에 대한 간단한 설명을 담은 `str`입니다. 마크다운을 포함할 수 있으며 문서 UI에 표시됩니다.
* `externalDocs`: 외부 문서를 설명하는 `dict`이며:
    * `description`: 외부 문서에 대한 간단한 설명을 담은 `str`입니다.
    * `url` (**필수**): 외부 문서의 URL을 담은 `str`입니다.

### 태그에 대한 메타데이터 생성 { #create-metadata-for-tags }

	}

	// Help for Identity Plugin
	Help = config.HelpKVS{
		config.HelpKV{
			Key:         URL,
			Description: `plugin hook endpoint (HTTP(S)) e.g. "http://localhost:8181/path/to/endpoint"` + defaultHelpPostfix(URL),
			Type:        "url",
		},
		config.HelpKV{
			Key:         AuthToken,
			Description: "authorization token for plugin hook endpoint" + defaultHelpPostfix(AuthToken),
			Optional:    true,
			Type:        "string",

      },
      "homePostalAddress" : {
        "type" : "keyword"
      },
      "labeledURI" : {
        "type" : "keyword"
      },
      "roomNumber" : {
        "type" : "keyword"
      },
      "description" : {
        "type" : "keyword"
      },
      "title" : {
        "type" : "keyword"
      },
      "pager" : {
        "type" : "keyword"
      },
      "street" : {
        "type" : "keyword"

    workspace: /dev/shm/elastic+elasticsearch+%BRANCH%+multijob+third-party-tests-gcs
    display-name: "elastic / elasticsearch # %BRANCH% - third party tests gcs"
    description: "Testing of the Elasticsearch %BRANCH% third party tests against GCS\n"
    builders:
      - inject:
          properties-file: '.ci/java-versions.properties'
          properties-content: |

import org.gradle.kotlin.dsl.support.expectedKotlinDslPluginsVersion

plugins {
    `kotlin-dsl`
}

group = "gradlebuild"

description = "Provides plugins used to create a Gradle plugin with Groovy or Kotlin DSL within build-logic builds"

dependencies {
    compileOnly(buildLibs.develocityPlugin)

    api(platform(projects.buildPlatform))

    implementation(projects.basics)
    implementation(projects.moduleIdentity)

from fastapi import Body, FastAPI
from pydantic import BaseModel

app = FastAPI()


class Item(BaseModel):
    name: str
    description: str | None = None
    price: float
    tax: float | None = None


class User(BaseModel):
    username: str
    full_name: str | None = None


@app.put("/items/{item_id}")
async def update_item(
    *,
    item_id: int,
    item: Item,
    user: User,

plugins {
    `kotlin-dsl`
}

description = "Provides plugins for configuring miscellaneous things (repositories, reproducibility, minify)"

group = "gradlebuild"

dependencies {
    api("gradlebuild:build-environment")
    api(platform(projects.buildPlatform))

    implementation(buildLibs.guava) {
        because("Used by class analysis")
    }
    implementation(libs.asm) {
        because("Used by class analysis")
    }

Les clés du `dict` identifient chaque exemple, et chaque valeur est un autre `dict`.

Chaque `dict` d'exemple spécifique dans `examples` peut contenir :

* `summary` : une courte description de l'exemple.
* `description` : une description longue qui peut contenir du texte Markdown.
* `value` : c'est l'exemple réel affiché, par ex. un `dict`.