///

## Abhängigkeitsfehler und -Rückgabewerte { #dependencies-errors-and-return-values }

Sie können dieselben Abhängigkeits-*Funktionen* verwenden, die Sie normalerweise verwenden.

### Abhängigkeitsanforderungen { #dependency-requirements }

Sie können Anforderungen für einen <abbr title="Request – Anfrage: Daten, die der Client zum Server sendet">Request</abbr> (wie Header) oder andere Unterabhängigkeiten deklarieren:

        MavenProject project = session.getCurrentProject();

        new ProjectBuilder(project)
                .addDependency(
                        "com.mycompany",
                        "system-dependency",
                        "1.0",
                        Artifact.SCOPE_SYSTEM,
                        new File(getBasedir(), "pom.xml").getAbsolutePath());

        Set<Artifact> artifactDependencies =

будет корректной для использования в качестве зависимости **FastAPI**.

На самом деле, FastAPI использует эти два декоратора внутренне.

///

## Зависимость базы данных с помощью `yield` { #a-database-dependency-with-yield }

Например, с его помощью можно создать сессию работы с базой данных и закрыть её после завершения.

Перед созданием ответа будет выполнен только код до и включая оператор `yield`:

      the current project.

      NOTE: This will likely contain much more than the direct dependencies of the
      current POM, since Maven uses transitive, or chained, dependency resolution.
    ]]></description>
  </expression>
  <expression>
    <syntax>project.parentArtifact</syntax>
    <configuration>
      <![CDATA[
    <parent>
      <groupId>project.group</groupId>

        verify(smbFile, times(1)).length();
        verifyNoMoreInteractions(smbFile);
    }

    @Test
    @DisplayName("accept: propagates SmbException thrown by dependency")
    void accept_propagatesSmbException() throws Exception {
        // Arrange: filter delegates to isDirectory which may throw SmbException
        SmbFileFilter filter = f -> f.isDirectory();

        <include>*.cmd</include>
        <include>*.conf</include>
        <include>*.java</include>
      </includes>
      <lineEnding>dos</lineEnding>
    </fileSet>
    <fileSet>
      <directory>target/dependency/org/jline/nativ</directory>
      <outputDirectory>lib/jline-native</outputDirectory>
      <includes>
        <include>**/*.so</include>
        <include>**/*.jnilib</include>
        <include>**/*.dll</include>

En este caso, puedes sobrescribir la dependencia que llama a ese proveedor y usar una dependencia personalizada que devuelva un usuario de prueba, solo para tus tests.

### Usa el atributo `app.dependency_overrides` { #use-the-app-dependency-overrides-attribute }

Para estos casos, tu aplicación **FastAPI** tiene un atributo `app.dependency_overrides`, es un simple `dict`.

    with pytest.raises((ValueError, Exception)):
        client.get("/broken-session-stream")


def test_broken_session_stream_no_raise():
    """
    When a dependency with yield raises after the streaming response already started
    the 200 status code is already sent, but there's still an error in the server
    afterwards, an exception is raised and captured or shown in the server logs.

### Das Attribut `app.dependency_overrides` verwenden { #use-the-app-dependency-overrides-attribute }

### Utilize o atributo `app.dependency_overrides` { #use-the-app-dependency-overrides-attribute }

Para estes casos, a sua aplicação **FastAPI** possui o atributo `app.dependency_overrides`. Ele é um simples `dict`.