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

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

import org.gradle.internal.exceptions.DefaultMultiCauseException
import org.gradle.tooling.events.FinishEvent
import org.gradle.tooling.events.OperationCompletionListener
import org.gradle.tooling.events.task.TaskFailureResult
import org.gradle.tooling.events.task.TaskFinishEvent
import org.gradle.tooling.events.task.TaskSuccessResult
import java.io.File
import java.io.FileOutputStream
import java.io.IOException

  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

    private static final Logger log = LoggerFactory.getLogger(WitnessClient.class);

    // Polling and backoff constants (in ms)
    private static final long MAX_POLL_INTERVAL = 5000; // Normal polling: max 5 seconds
    private static final long MAX_ERROR_BACKOFF = 30000; // Error polling: max 30 seconds
    private static final long BASE_POLL_INTERVAL = 1000;
    private static final long BASE_ERROR_DELAY = 1000;

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

            crawler.getCrawlerContext().setNumOfThread(numOfThread);
            final String sessionId = crawler.execute();

            // Wait for crawler to start running with polling
            long startTime = System.currentTimeMillis();
            while (crawler.crawlerContext.getStatus() != CrawlerStatus.RUNNING && System.currentTimeMillis() - startTime < 5000) {
                try {

    <!-- 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.+"/>

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