<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" />

  },
  {
    "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,

{* ../../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",

  "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.

                "createdBy");
        setupEpg(_epgMap, et -> ((BadWord) et).getCreatedTime(), (et, vl) -> ((BadWord) et).setCreatedTime(DfTypeUtil.toLong(vl)),
                "createdTime");
        setupEpg(_epgMap, et -> ((BadWord) et).getSuggestWord(), (et, vl) -> ((BadWord) et).setSuggestWord(DfTypeUtil.toString(vl)),
                "suggestWord");

        setupEpg(_epgMap, et -> ((BoostDocumentRule) et).getCreatedTime(),
                (et, vl) -> ((BoostDocumentRule) et).setCreatedTime(DfTypeUtil.toLong(vl)), "createdTime");
        setupEpg(_epgMap, et -> ((BoostDocumentRule) et).getSortOrder(),
                (et, vl) -> ((BoostDocumentRule) et).setSortOrder(DfTypeUtil.toInteger(vl)), "sortOrder");