import org.gradle.kotlin.dsl.register

/**
 * Plugin that pre-downloads Android SDK components to prevent race conditions during parallel builds.
 *
 * When multiple Android builds run in parallel and share the same `ANDROID_HOME`, the Android Gradle Plugin
 * may attempt to download and install SDK components (platforms, build-tools, platform-tools) simultaneously.
 * This can cause race conditions leading to:

  html_url: https://github.com/strawberry-graphql/strawberry
  stars: 4569
  owner_login: strawberry-graphql
  owner_html_url: https://github.com/strawberry-graphql
- name: chatgpt-web-share
  html_url: https://github.com/chatpire/chatgpt-web-share
  stars: 4294
  owner_login: chatpire
  owner_html_url: https://github.com/chatpire
- name: poem
  html_url: https://github.com/poem-web/poem
  stars: 4276
  owner_login: poem-web

* `ge`: `g`reater than or `e`qual
* `lt`: `l`ess `t`han
* `le`: `l`ess than or `e`qual

/// info

`Query`, `Path`, and other classes you will see later are subclasses of a common `Param` class.

All of them share the same parameters for additional validation and metadata you have seen.

///

/// note | Technical Details

When you import `Query`, `Path` and others from `fastapi`, they are actually functions.

## Caveat { #caveat }

If you need to perform heavy background computation and you don't necessarily need it to be run by the same process (for example, you don't need to share memory, variables, etc), you might benefit from using other bigger tools like <a href="https://docs.celeryq.dev" class="external-link" target="_blank">Celery</a>.

There's a high chance that the logic for your *startup* and *shutdown* is connected, you might want to start something and then finish it, acquire a resource and then release it, etc.

Doing that in separated functions that don't share logic or variables together is more difficult as you would need to store values in global variables or similar tricks.

Because of that, it's now recommended to instead use the `lifespan` as explained above.

  - navigation.instant.prefetch
  - navigation.instant.progress
  - navigation.path
  - navigation.tabs
  - navigation.tabs.sticky
  - navigation.top
  - navigation.tracking
  - search.highlight
  - search.share
  - search.suggest
  - toc.follow
  icon:
    repo: fontawesome/brands/github-alt
  logo: img/icon-white.svg
  favicon: img/favicon.png
  language: en
repo_name: fastapi/fastapi

            }
            if (path == null) {
                path = System.getenv("path");
            }
            final List<String> pathList = new ArrayList<>();
            pathList.add("/usr/share/fess/bin");
            if (path != null) {
                stream(path.split(File.pathSeparator)).of(stream -> stream.map(String::trim).forEach(s -> pathList.add(s)));
            }
            if (logger.isDebugEnabled()) {

Você apenas envia para `Depends` e o **FastAPI** sabe como fazer o resto.

///

## Compartilhando dependências `Annotated` { #share-annotated-dependencies }

Nos exemplos acima, você pode ver que existe uma pequena **duplicação de código**.

		<groupId>org.codelibs.fess</groupId>
		<artifactId>fess-parent</artifactId>
		<version>15.4.0</version>
		<relativePath />
	</parent>
	<properties>
		<!-- DEB & RPM build -->
		<packaging.fess.home.dir>/usr/share/fess</packaging.fess.home.dir>
		<packaging.fess.app.dir>${packaging.fess.home.dir}/app</packaging.fess.app.dir>
		<packaging.fess.bin.dir>${packaging.fess.home.dir}/bin</packaging.fess.bin.dir>

Solo la pasas a `Depends` y **FastAPI** sabe cómo hacer el resto.

///

## Compartir dependencias `Annotated` { #share-annotated-dependencies }

En los ejemplos anteriores, ves que hay un poquito de **duplicación de código**.