# Metadados e Urls de Documentos { #metadata-and-docs-urls }

Você pode personalizar várias configurações de metadados na sua aplicação **FastAPI**.

## Metadados para API { #metadata-for-api }

Você pode definir os seguintes campos que são usados na especificação OpenAPI e nas interfaces automáticas de documentação da API:

| Parâmetro | Tipo | Descrição |
|------------|------|-------------|
| `title` | `str` | O título da API. |

# Metadata and Docs URLs { #metadata-and-docs-urls }

You can customize several metadata configurations in your **FastAPI** application.

## Metadata for API { #metadata-for-api }

You can set the following fields that are used in the OpenAPI specification and the automatic API docs UIs:

| Parameter | Type | Description |
|------------|------|-------------|
| `title` | `str` | The title of the API. |

# Metadata y URLs de Docs { #metadata-and-docs-urls }

Puedes personalizar varias configuraciones de metadata en tu aplicación **FastAPI**.

## Metadata para la API { #metadata-for-api }

Puedes establecer los siguientes campos que se usan en la especificación OpenAPI y en las interfaces automáticas de documentación de la API:

| Parámetro | Tipo | Descripción |
|------------|------|-------------|
| `title` | `str` | El título de la API. |

# Metadaten und Dokumentations-URLs { #metadata-and-docs-urls }

Sie können mehrere Metadaten-Konfigurationen in Ihrer **FastAPI**-Anwendung anpassen.

## Metadaten für die API { #metadata-for-api }

Sie können die folgenden Felder festlegen, die in der OpenAPI-Spezifikation und in den Benutzeroberflächen der automatischen API-Dokumentation verwendet werden:

| Parameter | Typ | Beschreibung |
|------------|------|-------------|

# URL-адреса метаданных и документации { #metadata-and-docs-urls }

Вы можете настроить несколько конфигураций метаданных в вашем **FastAPI** приложении.

## Метаданные для API { #metadata-for-api }

Вы можете задать следующие поля, которые используются в спецификации OpenAPI и в UI автоматической документации API:

| Параметр | Тип | Описание |
|------------|------|-------------|
| `title` | `str` | Заголовок API. |

            RequestTrace trace,
            Metadata metadata,
            ArtifactRepository repository,
            VersionRangeResult result) {
        Versioning versioning = null;
        try {
            if (metadata != null) {
                try (SyncContext syncContext = syncContextFactory.newInstance(session, true)) {
                    syncContext.acquire(null, Collections.singleton(metadata));

            if (blob == null) {
                return Collections.emptyMap();
            }
            // GCS uses metadata instead of tags
            final Map<String, String> metadata = blob.getMetadata();
            return metadata != null ? new HashMap<>(metadata) : Collections.emptyMap();
        } catch (final Exception e) {
            throw new StorageException("Failed to get tags from " + objectName, e);

                }
            }

            if (includeContent) {
                // Add blob metadata as response metadata (only when content is included)
                final Map<String, String> blobMetadata = blob.getMetadata();
                if (blobMetadata != null) {
                    blobMetadata.forEach(responseData::addMetaData);
                }

        RepositoryMetadata metadata = new ArtifactRepositoryMetadata(a);

        File file = new File(
                localRepository.getBasedir(), localRepository.pathOfLocalRepositoryMetadata(metadata, localRepository));
        file.delete();

        File touchFile = updateCheckManager.getTouchfile(metadata, file);
        touchFile.delete();

    public boolean isUpdateRequired(RepositoryMetadata metadata, ArtifactRepository repository, File file) {
        // Here, we need to determine which policy to use. Release updateInterval will be used when
        // the metadata refers to a release artifact or meta-version, and snapshot updateInterval will be used when
        // it refers to a snapshot artifact or meta-version.