你也可以通过参数 `openapi_tags` 为用于分组路径操作的不同标签添加额外的元数据。

它接收一个列表，列表中每个标签对应一个字典。

每个字典可以包含：

- `name`（必填）：一个 `str`，与在你的*路径操作*和 `APIRouter` 的 `tags` 参数中使用的标签名相同。
- `description`：一个 `str`，该标签的简短描述。可以使用 Markdown，并会显示在文档 UI 中。
- `externalDocs`：一个 `dict`，描述外部文档，包含：
    - `description`：一个 `str`，该外部文档的简短描述。
    - `url`（必填）：一个 `str`，该外部文档的 URL。

### 创建标签元数据 { #create-metadata-for-tags }

让我们在带有标签的示例中为 `users` 和 `items` 试一下。

  CHECK_EQ(actual, 1);
}

TFE_MonitoringCounter0* CreateCounter0(const char* counter_name) {
  TF_Status* status = TF_NewStatus();
  auto* counter =
      TFE_MonitoringNewCounter0(counter_name, status, "description");
  TF_DeleteStatus(status);
  return counter;
}

void IncrementCounter0(TFE_MonitoringCounter0* counter, int64_t delta) {
  auto* cell = TFE_MonitoringGetCellCounter0(counter);

  <groupId>com.example.group</groupId>
  <artifactId>valid-version-sha1plus</artifactId>
  <version>${sha1}${wrong}${revision}</version>

  <description>
    This will test if the validation for the ci friendly versions
    is working correct.
  </description>

                        "responses": {
                            "200": {
                                "description": "Successful Response",
                                "content": {"application/json": {"schema": {}}},
                            },
                            "422": {
                                "description": "Validation Error",
                                "content": {

	HelpCallhome = config.HelpKVS{
		config.HelpKV{
			Key:         Enable,
			Type:        "on|off",
			Description: "set to enable callhome" + defaultHelpPostfix(Enable),
			Optional:    true,
		},
		config.HelpKV{
			Key:         Frequency,
			Type:        "duration",
			Description: "time duration between callhome cycles e.g. 24h" + defaultHelpPostfix(Frequency),
			Optional:    true,
		},
	}

from fastapi import FastAPI, Security
from fastapi.security import HTTPAuthorizationCredentials, HTTPBearer
from fastapi.testclient import TestClient
from inline_snapshot import snapshot

app = FastAPI()

security = HTTPBearer(description="HTTP Bearer token scheme")


@app.get("/users/me")
def read_current_user(credentials: HTTPAuthorizationCredentials = Security(security)):
    return {"scheme": credentials.scheme, "credentials": credentials.credentials}

{
    "responses": {
        "404": {
            "description": "Additional Response",
            "content": {
                "application/json": {
                    "schema": {
                        "$ref": "#/components/schemas/Message"
                    }
                }
            }
        },
        "200": {
            "description": "Successful Response",
            "content": {

// minioCollector is the Custom Collector
type minioCollector struct {
	desc *prometheus.Desc
}

// Describe sends the super-set of all possible descriptors of metrics
func (c *minioCollector) Describe(ch chan<- *prometheus.Desc) {
	ch <- c.desc
}

// Collect is called by the Prometheus registry when collecting metrics.
func (c *minioCollector) Collect(ch chan<- prometheus.Metric) {
	// Expose MinIO's version information

## ドキュメントの概要と説明 - OpenAPI { #documentation-summary-and-description-openapi }

*path operations* に概要と説明を追加し、ドキュメント UI に表示するには、[チュートリアル - path operation の設定 - 概要と説明](../tutorial/path-operation-configuration.md#summary-and-description) を参照してください。

## ドキュメントのレスポンス説明 - OpenAPI { #documentation-response-description-openapi }

                                        <label for="description" class="col-sm-2 text-sm-right col-form-label"><la:message
                                                key="labels.description"/></label>
                                        <div class="col-sm-10">
                                            <la:text styleId="description" property="description"
                                                     styleClass="form-control"/>