그 전에는, 하나의 예제만 가능한 `example` 키워드만 지원했습니다. 이는 아직 OpenAPI 3.1.0에서 지원하지만, 지원이 종료될 것이며 JSON 스키마 표준에 포함되지 않습니다. 그렇기에 `example`을 `examples`으로 이전하는 것을 추천합니다. 🤓

이 문서 끝에 더 많은 읽을거리가 있습니다.

///

## `Field` 추가 인자

Pydantic 모델과 같이 `Field()`를 사용할 때 추가적인 `examples`를 선언할 수 있습니다:

{* ../../docs_src/schema_extra_example/tutorial002_py310.py hl[2,8:11] *}

## JSON Schema에서의 `examples` - OpenAPI

이들 중에서 사용합니다:

* `Path()`

		return nil
	}
	val := int(n.NoncurrentDays)
	switch {
	case val == 0 && n.NewerNoncurrentVersions == 0:
		// both fields can't be zero
		return errXMLNotWellFormed

	case val < 0, n.NewerNoncurrentVersions < 0:
		// negative values are not supported
		return errXMLNotWellFormed
	}
	return nil
}

// NoncurrentVersionTransition - an action for lifecycle configuration rule.
type NoncurrentVersionTransition struct {

      <version>1.0.0+</version>
      <fields>
        <field>
          <name>groupId</name>
          <description>The group ID of the extension's artifact.</description>
          <version>1.0.0+</version>
          <required>true</required>
          <type>String</type>
        </field>
        <field>
          <name>artifactId</name>

        // Then
        // Verify that the 'sam' field is set correctly
        assertEquals(mockSamArray, msrpc.sam, "The 'sam' field should be initialized with the provided SamrSamArray.");

        // Verify that the 'ptype' field is set to 0
        assertEquals(0, msrpc.getPtype(), "The 'ptype' field should be initialized to 0.");

        // Verify that the 'flags' field is set to DCERPC_FIRST_FRAG | DCERPC_LAST_FRAG

    is_coroutine: bool = True,
    endpoint_ctx: Optional[EndpointContext] = None,
) -> Any:
    if field:
        errors = []
        if is_coroutine:
            value, errors_ = field.validate(response_content, {}, loc=("response",))
        else:
            value, errors_ = await run_in_threadpool(
                field.validate, response_content, {}, loc=("response",)
            )
        if isinstance(errors_, list):

        Field field = response.getClass().getDeclaredField("converter");
        field.setAccessible(true);
        return field.getInt(response);
    }

    private void setConverter(NetServerEnum2Response response, int value) throws Exception {
        Field field = response.getClass().getDeclaredField("converter");
        field.setAccessible(true);
        field.setInt(response, value);
    }

      <name>Metadata</name>
      <version>1.0.0+</version>
      <fields>
        <field xml.attribute="true" xml.tagName="modelVersion">
          <name>modelVersion</name>
          <version>1.1.0+</version>
          <type>String</type>
          <description>The version of the underlying metadata model.</description>
        </field>
        <field>
          <name>groupId</name>
          <version>1.0.0+</version>

The `HeroUpdate` *data model* is somewhat special, it has **all the same fields** that would be needed to create a new hero, but all the fields are **optional** (they all have a default value). This way, when you update a hero, you can send just the fields that you want to update.

Because all the **fields actually change** (the type now includes `None` and they now have a default value of `None`), we need to **re-declare** them.

 * </ul>
 *
 * <p>Fields:
 * <ul>
 * <li>{@link #logger} - Logger instance.
 * <li>{@link #client} - OpenSearch client.
 * <li>{@link #index} - Index name.
 * <li>{@link #settings} - Suggest settings.
 * <li>{@link #supportedFields} - Supported fields for suggestions.
 * <li>{@link #tagFieldNames} - Tag field names.
 * <li>{@link #roleFieldName} - Role field name.

      <description>A plugin parameter expression supported by Maven</description>
      <fields>
        <field>
          <version>1.0.0</version>
          <name>syntax</name>
          <description>The syntax of the expression</description>
          <type>String</type>
          <required>true</required>
        </field>
        <field>
          <version>1.0.0</version>
          <name>description</name>