# Background Tasks - `BackgroundTasks`

You can declare a parameter in a *path operation function* or dependency function with the type `BackgroundTasks`, and then you can use it to schedule the execution of background tasks after the response is sent.

You can import it directly from `fastapi`:

```python
from fastapi import BackgroundTasks
```

        //     <dependencies>
        //         <!--  Yoko modules -->
        //         <dependency>
        //             <groupId>org.apache.yoko</groupId>
        //             <artifactId>yoko-core</artifactId>
        //             <version>${version}</version>
        //         </dependency>
        // ...
        //
        // And the range is not set so we'll check here and set it. jvz.

Each process, or "runtime", applies different constraints to the code that runs in that process.
For example, each process has different supported JVMs and a different set of services available for dependency injection.
While a lot of Gradle source code runs only in the Gradle daemon, not all of it does so.

/**
 * Base interface for service requests that involve remote repository operations.
 * This interface provides common functionality for requests that need to specify
 * and validate remote repositories for artifact resolution, dependency collection,
 * model building, and other Maven operations.
 *
 * <p>Implementations of this interface can specify a list of remote repositories
 * to be used during the operation. If no repositories are specified (null),

## Basit HTTP Basic Auth { #simple-http-basic-auth }

* `HTTPBasic` ve `HTTPBasicCredentials` import edin.
* `HTTPBasic` kullanarak bir "`security` scheme" oluşturun.
* *path operation*’ınızda bir dependency ile bu `security`’yi kullanın.
* Bu, `HTTPBasicCredentials` tipinde bir nesne döndürür:
    * İçinde gönderilen `username` ve `password` bulunur.

{* ../../docs_src/security/tutorial006_an_py310.py hl[4,8,12] *}

            val details = info.details
            if (!details.requiredRuntimes.isEmpty()) {
                (details.dependencies + path).forEach { dependency ->
                    details.requiredRuntimes.forEach { requiredRuntime ->
                        computedTargetRuntimes.getOrPut(dependency) {
                            mutableMapOf()
                        }.getOrPut(requiredRuntime) {
                            mutableSetOf()

# Request Parameters

Here's the reference information for the request parameters.

These are the special functions that you can put in *path operation function* parameters or dependency functions with `Annotated` to get data from the request.

It includes:

* `Query()`
* `Path()`
* `Body()`
* `Cookie()`
* `Header()`
* `Form()`
* `File()`

You can import them all directly from `fastapi`:

```python

            String groupId, String artifactId, String version, String type, String classifier);

    Artifact createPluginArtifact(Plugin plugin);

    Artifact createDependencyArtifact(Dependency dependency);

    ArtifactRepository buildArtifactRepository(Repository repository) throws InvalidRepositoryException;

    ArtifactRepository createDefaultRemoteRepository() throws InvalidRepositoryException;

    }

    /**
     * Gets the scope of (transitive) dependencies that should be collected. Dependency collection refers to the process
     * of calculating the complete dependency tree in terms of artifact coordinates. In contrast to dependency
     * resolution, this does not include the download of the files for the dependency artifacts. It is meant for mojos

MockWebServer for JUnit 4
=========================

This module integrates mockwebserver3.MockWebServer with JUnit 4.

To use, first add this library as a test dependency:

```
testImplementation("com.squareup.okhttp3:mockwebserver3-junit4:5.3.0")
```

Then in tests annotated `@org.junit.Test`, you may declare a field with the `@Rule` annotation:

```
@Rule public final MockWebServerRule serverRule = new MockWebServerRule();
```