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

			{
				"parallelizationMethod":{
					"name":"TestDistribution"
				},
				"subprojects":[
					"kotlin-dsl-tooling-builders",
					"build-events",
					"resources-s3",
					"plugins-jvm-test-suite",
					"plugins-version-catalog",
					"plugins-application",
					"reporting",
					"tooling-native",
					"language-jvm",
					"instrumentation-reporting",
					"plugins-java-library"
				]
			},
			{

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

# Core automation platform (Declarative DSL)

            builtBy(localPublish)
        }
    }

    if (signArtifacts) {
        // Otherwise we get
        // ask ':tooling-api:publishGradleDistributionPublicationToRemoteRepository' uses this output of task ':tooling-api:signLocalPublication'
        // without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.

{!> ../../docs_src/response_model/tutorial003_01.py!}
```

////

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

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

        content {
            includeGroup("net.rubygrapefruit")
            includeGroup("org.gradle.fileevents")
            includeModule("flot", "flot")
            includeModule("org.gradle", "gradle-tooling-api")
            includeModule("org.gradle.buildtool.internal", "configuration-cache-report")
            includeModule("org.gradle.buildtool.internal", "gradle-ide-starter")
        }
    }
    google {

h3. Plugins

* Execution model
* Metadata model
* Metadata tooling
 ** Metadata extractor
 ** Metadata reader
 ** Metadata writer
 ** Metadata adapter (if required for the target system)
* Maven packaging and lifecycle
* Maven test harness for plugin execution model
* Eclipse IDE tooling for plugin execution model and metadata model

- we also seem to have information like the plugin lifecycle model that's buried inside the maven execution model

/// tip

Some editors check for unused function parameters, and show them as errors.

Using these `dependencies` in the *path operation decorator* you can make sure they are executed while avoiding editor/tooling errors.

It might also help avoid confusion for new developers that see an unused parameter in your code and could think it's unnecessary.

///

/// info

  "durations" : [ {
    "testProject" : "largeJavaMultiProject",
    "linux" : 886
  } ]
}, {
  "scenario" : "org.gradle.performance.regression.java.JavaIDETaskExecutionPerformanceTest.run clean assemble via Tooling API",
  "durations" : [ {
    "testProject" : "largeAndroidBuild",
    "linux" : 549
  }, {
    "testProject" : "largeJavaMultiProject",
    "linux" : 687
  }, {

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