issues:
  # Which dirs to exclude: issues from them won't be reported.
  # Can use regexp here: `generated.*`, regexp is applied on full path,
  # including the path prefix if one is set.
  # Default dirs are skipped independently of this option's value (see exclude-dirs-use-default).
  # "/" will be replaced by current OS file path separator to properly work on Windows.
  # Default: []
  exclude-dirs:
    - genfiles$
    - vendor$

    implementation(project(":binary-compatibility"))

    implementation("org.codenarc:CodeNarc") {
        exclude(group = "org.apache.groovy")
        exclude(group = "org.codehaus.groovy")
    }
    implementation("com.github.javaparser:javaparser-symbol-solver-core") {
        exclude(group = "com.google.guava")
    }
    implementation("org.gradle.kotlin:gradle-kotlin-dsl-conventions")

        additional-arguments: --no-configuration-cache
      env:
        # Exclude some projects and configurations that should not contribute to the dependency graph
        DEPENDENCY_GRAPH_EXCLUDE_PROJECTS: ':docs|:internal-performance-testing|:enterprise-plugin-performance|:performance|:internal-integ-testing'

!!! info
    You can also use:

    * `response_model_exclude_defaults=True`
    * `response_model_exclude_none=True`

    as described in <a href="https://docs.pydantic.dev/latest/concepts/serialization/#modeldict" class="external-link" target="_blank">the Pydantic docs</a> for `exclude_defaults` and `exclude_none`.

    public void testIsTargetProperty_excludes_prefix() throws Exception {
        final CopyOptions option = new CopyOptions().prefix(BeanNames.abc_()).exclude(BeanNames.abc_exclude());
        assertThat(option.isTargetProperty("abc_value"), is(true));
        assertThat(option.isTargetProperty("abc_exclude"), is(not(true)));
        assertThat(option.isTargetProperty("ab"), is(not(true)));
    }

    /**
     * @throws Exception
     */

            <!-- Yes, we want to exclude ForceGuavaCompilation 4 times: -->
            <!-- (And we might as well exclude DummyJavadocClass 3 times (though it would be harmless to include).) -->
            <!-- 1. Don't compile it (since that requires a *non-test* dep on gwt-user. -->
            <exclude>**/ForceGuavaCompilation*</exclude>
            <exclude>**/DummyJavadocClass*</exclude>
          </excludes>
        </configuration>

    /**
     *
     */
    public String xyz_value = "xyz";

    /**
     *
     */
    public String other = "other";

    /**
     *
     */
    public String abc_exclude = "exclude";

    /**
     *
     */
    public String ab = "ab";

    `PATCH` 没有 `PUT` 知名，也怎么不常用。

    很多人甚至只用 `PUT` 实现部分更新。

    **FastAPI** 对此没有任何限制，可以**随意**互换使用这两种操作。

    但本指南也会分别介绍这两种操作各自的用途。

### 使用 Pydantic 的 `exclude_unset` 参数

更新部分数据时，可以在 Pydantic 模型的 `.dict()` 中使用 `exclude_unset` 参数。

比如，`item.dict(exclude_unset=True)`。

这段代码生成的 `dict` 只包含创建 `item` 模型时显式设置的数据，而不包括默认值。

然后再用它生成一个只含已设置（在请求中所发送）数据，且省略了默认值的 `dict`：

```Python hl_lines="34"

!!! info "정보"
    아래 또한 사용할 수 있습니다:

    * `response_model_exclude_defaults=True`
    * `response_model_exclude_none=True`

    <a href="https://docs.pydantic.dev/latest/concepts/serialization/#modeldict" class="external-link" target="_blank">Pydantic 문서</a>에서 `exclude_defaults` 및 `exclude_none`에 대해 설명한 대로 사용할 수 있습니다.

#### 기본값이 있는 필드를 갖는 값의 데이터

!!! info "Информация"
    Вы также можете использовать:

    * `response_model_exclude_defaults=True`
    * `response_model_exclude_none=True`