## Dependency Injection { #dependency-injection }

Using `BackgroundTasks` also works with the dependency injection system, you can declare a parameter of type `BackgroundTasks` at multiple levels: in a *path operation function*, in a dependency (dependable), in a sub-dependency, etc.

이것을 해결하는 일은 **FastAPI**가 알아서 처리합니다.

## 첫 번째 의존성 "dependable" { #first-dependency-dependable }

다음과 같이 첫 번째 의존성("dependable")을 만들 수 있습니다:

{* ../../docs_src/dependencies/tutorial005_an_py310.py hl[8:9] *}

이 의존성은 선택적 쿼리 파라미터 `q`를 `str`로 선언하고, 그대로 반환합니다.

매우 단순한 예시(그다지 유용하진 않음)이지만, 하위 의존성이 어떻게 동작하는지에 집중하는 데 도움이 됩니다.

## 두 번째 의존성 "dependable"과 "dependant" { #second-dependency-dependable-and-dependant }

你可以建立具有「子相依」的相依項。

它們可以按你的需要，層級任意加深。

**FastAPI** 會負責解析它們。

## 第一個相依項 "dependable" { #first-dependency-dependable }

你可以建立第一個相依項（"dependable"）如下：

{* ../../docs_src/dependencies/tutorial005_an_py310.py hl[8:9] *}

它宣告了一個可選的查詢參數 `q`（型別為 `str`），然後直接回傳它。

這很簡單（不太實用），但有助於我們專注於子相依如何運作。

## 第二個相依，同時是 "dependable" 也是 "dependant" { #second-dependency-dependable-and-dependant }

接著你可以建立另一個相依函式（"dependable"），同時它也宣告了自己的相依（因此它同時也是 "dependant"）：

      <url>file://dummy</url>
    </repository>
  </repositories>
  <dependencies>
    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t06-b</artifactId>
      <version>1.0</version>
      <type>jar</type>
      <scope>compile</scope>
    </dependency>
  </dependencies>

      <url>file://dummy</url>
    </repository>
  </repositories>
  <dependencies>
    <dependency>
      <groupId>maven-test</groupId>
      <artifactId>t07-b</artifactId>
      <version>1.0</version>
      <type>jar</type>
      <scope>compile</scope>
    </dependency>
  </dependencies>

    }
)

client = TestClient(app)


def raise_value_error():
    raise ValueError()


def dependency_with_yield():
    yield raise_value_error()


@app.get("/dependency-with-yield", dependencies=[Depends(dependency_with_yield)])
def with_yield(): ...


@app.get("/http-exception")
def route_with_http_exception():
    raise HTTPException(status_code=400)

    }

    public boolean isResolved() {
        return children != null;
    }

    /**
     * Test whether the node is direct or transitive dependency.
     *
     * @return whether the node is direct or transitive dependency
     */
    public boolean isChildOfRootNode() {
        return parent != null && parent.parent == null;
    }

    public Iterator<ResolutionNode> getChildrenIterator() {

        assertNotNull(new DependencyManagement().toString());
    }

    @Test
    void testDependencies() {
        DependencyManagement dm = new DependencyManagement();
        Dependency d1 = new Dependency();
        d1.setGroupId("myGroupId");
        assertNotNull(dm.getDependencies());
        assertEquals(0, dm.getDependencies().size());
        dm.addDependency(d1);
        assertNotNull(dm.getDependencies());

                    if (pointer instanceof Lifecycle.DependenciesPointer) {
                        // For dependencies: ensure current project's phase starts after dependency's phase completes
                        // Example: project's compile starts after dependency's package completes
                        // TODO: String scope = ((Lifecycle.DependenciesPointer) pointer).scope();
                        projects.get(project)

This document formally describes the process of addressing and managing a
reported vulnerability that has been found in the MinIO server code base,
any directly connected ecosystem component or a direct / indirect dependency
of the code base.

## Scope

The vulnerability management policy described in this document covers the
process of investigating, assessing and resolving a vulnerability report