},
  {
    "name": "declarative-dsl-tooling-builders",
    "path": "platforms/core-configuration/declarative-dsl-tooling-builders",
    "unitTests": false,
    "functionalTests": false,
    "crossVersionTests": true
  },
  {
    "name": "declarative-dsl-tooling-models",
    "path": "platforms/core-configuration/declarative-dsl-tooling-models",
    "unitTests": false,
    "functionalTests": false,

            <option value="$PROJECT_DIR$/platforms/core-configuration/declarative-dsl-provider" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/declarative-dsl-tooling-builders" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/declarative-dsl-tooling-models" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/dependency-management-serialization-codecs" />

  stars: 3379
  owner_login: TracecatHQ
  owner_html_url: https://github.com/TracecatHQ
- name: opyrator
  html_url: https://github.com/ml-tooling/opyrator
  stars: 3135
  owner_login: ml-tooling
  owner_html_url: https://github.com/ml-tooling
- name: docarray
  html_url: https://github.com/docarray/docarray
  stars: 3114
  owner_login: docarray
  owner_html_url: https://github.com/docarray

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

With this, we get tooling support, from editors and mypy as this code is correct in terms of types, but we also get the data filtering from FastAPI.

How does this work? Let's check that out. 🤓

### Type Annotations and Tooling { #type-annotations-and-tooling }

First let's see how editors, mypy and other tools would see this.

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.

        List<String> excludedPackages = new ArrayList<>();
        // These are part of the API, but not the DSL
        excludedPackages.add("org.gradle.tooling.**");
        excludedPackages.add("org.gradle.testfixtures.**");

        // Tweak the imports due to some inconsistencies introduced before we automated the default-imports generation

      "coverage" : {
        "per_commit" : [ "linux" ]
      }
    } ]
  }, {
    "testId" : "org.gradle.performance.regression.java.JavaIDETaskExecutionPerformanceTest.run compileJava via Tooling API",
    "groups" : [ {
      "testProject" : "largeAndroidBuild",
      "coverage" : {
        "per_commit" : [ "linux" ]
      }
    }, {
      "testProject" : "largeJavaMultiProject",

fun Project.isPerformanceProject() = setOf("build-scan-performance", "performance").contains(name)

fun Project.isNativeProject() = name.contains("native")

fun Project.isKotlinDslToolingBuilders() = name.contains("kotlin-dsl-tooling-builders")

/**
 * Whether the project supports running with predictive test selection.
 *
 * Our performance tests don't work with PTS, yet.

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

Como isso funciona? Vamos verificar. 🤓

### Anotações de tipo e ferramentas { #type-annotations-and-tooling }

Primeiro, vamos ver como editores, mypy e outras ferramentas veriam isso.