///

## Помилки залежностей і значення, що повертаються { #dependencies-errors-and-return-values }

Ви можете використовувати ті самі *функції* залежностей, що й зазвичай.

### Вимоги залежностей { #dependency-requirements }

Вони можуть оголошувати вимоги до запиту (наприклад, заголовки) або інші підзалежності:

{* ../../docs_src/dependencies/tutorial006_an_py310.py hl[8,13] *}

### Підіймати винятки { #raise-exceptions }

        super("stopwords.*\\.txt");
    }

    /**
     * Registers this creator with the dictionary manager upon initialization.
     * This method is annotated with {@link PostConstruct} to be executed after
     * dependency injection is complete.
     */
    @PostConstruct
    public void register() {
        if (logger.isInfoEnabled()) {
            logger.info("Loaded {}", this.getClass().getSimpleName());
        }

import java.util.Iterator;
import java.util.NoSuchElementException;
import org.jspecify.annotations.Nullable;

/**
 * Note this class is a copy of {@link com.google.common.collect.AbstractIterator} (for dependency
 * reasons).
 */
@GwtCompatible
abstract class AbstractIterator<T extends @Nullable Object> implements Iterator<T> {
  private State state = State.NOT_READY;

  protected AbstractIterator() {}

* the child class
* the sibling class
* the class method

* the header
* the headers
* the authorization header
* the `Authorization` header
* the forwarded header

* the dependency injection system
* the dependency
* the dependable
* the dependant

* I/O bound
* CPU bound
* concurrency
* parallelism
* multiprocessing

* the env var
* the environment variable
* the `PATH`

## Gérer les erreurs et les valeurs de retour des dépendances { #dependencies-errors-and-return-values }

Vous pouvez utiliser les mêmes *fonctions* de dépendance que d'habitude.

### Définir les exigences des dépendances { #dependency-requirements }

Elles peuvent déclarer des exigences pour la requête (comme des en-têtes) ou d'autres sous-dépendances :

{* ../../docs_src/dependencies/tutorial006_an_py310.py hl[8,13] *}

    "crossVersionTests": false
  },
  {
    "name": "dependency-management",
    "path": "platforms/software/dependency-management",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": true
  },
  {
    "name": "dependency-management-serialization-codecs",
    "path": "platforms/core-configuration/dependency-management-serialization-codecs",
    "unitTests": false,

-->

#### What type of PR is this?

<!--
Add one of the following kinds:
/kind bug
/kind dependency
/kind cleanup
/kind documentation
/kind feature

Optionally add one or more of the following kinds if applicable:
/kind api-change
/kind deprecation
/kind failing-test
/kind flake
/kind regression

Bu yüzden onları ayrı bir `dependencies` module’üne koyuyoruz (`app/dependencies.py`).

Şimdi, özel bir `X-Token` header'ını okumak için basit bir dependency kullanalım:

{* ../../docs_src/bigger_applications/app_an_py310/dependencies.py hl[3,6:8] title["app/dependencies.py"] *}

/// tip | İpucu

Örneği basit tutmak için uydurma bir header kullanıyoruz.

    public FileTypeHelper() {
        // Default constructor
    }

    /**
     * Initializes the file type mappings by loading configuration from Fess settings.
     * This method is called automatically after dependency injection is complete.
     * The mappings are loaded from the index filetype configuration property,
     * where each line contains a MIME type to file type mapping in the format "mimetype=filetype".
     */

在這個範例中我們使用了自訂的（虛構的）標頭 `X-Key` 與 `X-Token`。

但在實際情況下，當你實作安全機制時，使用整合的 [Security utilities（下一章）](../security/index.md) 會獲得更多好處。

///

## 依賴的錯誤與回傳值 { #dependencies-errors-and-return-values }

你可以使用與平常相同的依賴函式。

### 依賴的需求 { #dependency-requirements }

它們可以宣告請求需求（例如標頭（headers））或其他子依賴：

{* ../../docs_src/dependencies/tutorial006_an_py310.py hl[8,13] *}

### 拋出例外 { #raise-exceptions }

這些依賴可以 `raise` 例外，與一般依賴相同：