<option value="$PROJECT_DIR$/platforms/core-configuration/kotlin-dsl-tooling-builders" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/kotlin-dsl-tooling-model-impls" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/kotlin-dsl-tooling-models" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/model-core" />

      {
        "subprojects": [
          "declarative-dsl-provider",
          "declarative-dsl-tooling-builders",
          "enterprise",
          "execution-e2e-tests",
          "file-collections",
          "ide-plugins",
          "integ-test",
          "ivy",
          "jacoco",
          "kotlin-dsl-tooling-builders",
          "language-groovy",
          "maven",
          "platform-native",

  {
    "name": "tooling-api-provider",
    "path": "platforms/core-runtime/tooling-api-provider",
    "unitTests": false,
    "functionalTests": false,
    "crossVersionTests": false
  },
  {
    "name": "tooling-native",
    "path": "platforms/native/tooling-native",
    "unitTests": false,
    "functionalTests": false,
    "crossVersionTests": true
  },
  {
    "name": "tooling-native-model-impls",

  stars: 3501
  owner_login: IBM
  owner_html_url: https://github.com/IBM
- name: opyrator
  html_url: https://github.com/ml-tooling/opyrator
  stars: 3137
  owner_login: ml-tooling
  owner_html_url: https://github.com/ml-tooling
- name: docarray
  html_url: https://github.com/docarray/docarray
  stars: 3120
  owner_login: docarray
  owner_html_url: https://github.com/docarray

platforms/core-configuration/kotlin-dsl-plugins/            @gradle/bt-tide
platforms/core-configuration/kotlin-dsl-provider-plugins/   @gradle/bt-tide
platforms/core-configuration/kotlin-dsl-tooling-builders/   @gradle/bt-tide
platforms/core-configuration/kotlin-dsl-tooling-models/     @gradle/bt-tide

# Core automation platform (Declarative DSL)
platforms/core-configuration/declarative-dsl-api/                   @gradle/bt-declarative-gradle-project

        )

        // TODO: Gradle profiler should use the bundled tooling API.
        //   This should actually be handled by conflict resolution, though it doesn't seem to work.
        //   See https://github.com/gradle/gradle/issues/12002.
        applyRule<DependencyRemovalByNameRule>(
            "org.gradle.profiler:gradle-profiler",
            setOf("gradle-tooling-api")
        )
    }
}

    <!-- Protocol types may only define constants in interfaces -->
    <suppress checks="InterfaceIsTypeCheck"
              files=".*[/\\]tooling-api[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]tooling[/\\]internal[/\\]protocol.+"/>
    <suppress checks="InterfaceIsTypeCheck"
              files=".*[/\\]core-api[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]api[/\\]attributes[/\\]Usage.+"/>

  "durations" : [ {
    "testProject" : "largeJavaMultiProject",
    "linux" : 1018
  } ]
}, {
  "scenario" : "org.gradle.performance.regression.java.JavaIDETaskExecutionPerformanceTest.run compileJava via Tooling API",
  "durations" : [ {
    "testProject" : "largeAndroidBuild",
    "linux" : 1351
  }, {
    "testProject" : "largeJavaMultiProject",
    "linux" : 734
  }, {

{* ../../docs_src/response_model/tutorial003_01_py310.py hl[7:10,13:14,18] *}

這樣我們能得到工具支援，對於編輯器與 mypy 來說，這段程式碼在型別上是正確的，同時我們也能得到 FastAPI 的資料過濾。

這是怎麼運作的？來看一下。🤓

### 型別註解與工具支援 { #type-annotations-and-tooling }

先看看編輯器、mypy 與其他工具會怎麼看這件事。

`BaseUser` 有基礎欄位。然後 `UserIn` 繼承自 `BaseUser` 並新增 `password` 欄位，因此它會包含兩個模型的所有欄位。

我們把函式回傳型別註解為 `BaseUser`，但實際上回傳的是 `UserIn` 實例。

Wie funktioniert das? Schauen wir uns das mal an. 🤓

### Typannotationen und Tooling { #type-annotations-and-tooling }

Sehen wir uns zunächst an, wie Editor, mypy und andere Tools dies sehen würden.