* Obtener el resultado de tu función.
* Asignar ese resultado al parámetro en tu *path operation function*.

```mermaid
graph TB

common_parameters(["common_parameters"])
read_items["/items/"]
read_users["/users/"]

common_parameters --> read_items
common_parameters --> read_users
```

De esta manera escribes código compartido una vez y **FastAPI** se encarga de llamarlo para tus *path operations*.

```plaintext
/home/user/code/awesome-project/.venv/bin/python
```

ve onu kullanır.

////

//// tab | Windows

```plaintext
C:\Users\user\code\awesome-project\.venv\Scripts;C:\Windows\System32
```

Bu, sistemin artık programları önce şurada aramaya başlayacağı anlamına gelir:

```plaintext
C:\Users\user\code\awesome-project\.venv\Scripts
```

   * @since 33.4.0 (but since 28.0 in the JRE flavor)
   */
  @J2ktIncompatible
  @GwtIncompatible // java.util.concurrent.ScheduledExecutorService
  @IgnoreJRERequirement // Users will use this only if they're already using Duration.
  // TODO(cpovirk): Return ListenableScheduledFuture?
  public static <O extends @Nullable Object> ListenableFuture<O> scheduleAsync(

        Be aware, though: most feature requests are not accepted, even if they're suggested by
        a full-time Guava team member. [Feedback](https://stackoverflow.com/a/4543114) from our
        users indicates that they really appreciate Guava's high power-to-weight ratio. It's
        important to us to keep Guava as easy to use and understand as we can. That means boiling

    * `url` (**обов'язково**): `str` з URL-адресою зовнішньої документації.

### Створення метаданих для тегів { #create-metadata-for-tags }

Спробуймо це на прикладі з тегами для `users` та `items`.

Створіть метадані для своїх тегів і передайте їх у параметр `openapi_tags`:

{* ../../docs_src/metadata/tutorial004_py310.py hl[3:16,18] *}

    display-name: "elastic / elasticsearch - pull request part-1 windows"
    description: "Testing of Elasticsearch pull requests - part-1 windows"
    node: "windows-immutable"
    workspace: "C:\\Users\\jenkins\\workspace\\pr-part-1\\${BUILD_NUMBER}"
    scm:
      - git:
          refspec: "+refs/pull/${ghprbPullId}/*:refs/remotes/origin/pr/${ghprbPullId}/*"
          branches:
            - "${ghprbActualCommit}"

On the other side, there are thousands of users in the chat systems, so there's a high chance you'll find someone to talk to there, almost all the time. 😄

## Sponsor the author { #sponsor-the-author }

   *
   * @throws IOException if an I/O error occurs while writing to this sink
   * @since 33.4.0 (but since 22.0 in the JRE flavor)
   */
  @IgnoreJRERequirement // Users will use this only if they're already using Stream.
  public void writeLines(Stream<? extends CharSequence> lines) throws IOException {
    writeLines(lines, LINE_SEPARATOR.value());
  }

  /**

    * `url` (**erforderlich**): ein `str` mit der URL für die externe Dokumentation.

### Metadaten für Tags erstellen { #create-metadata-for-tags }

Versuchen wir es mit einem Beispiel mit Tags für `users` und `items`.

Erstellen Sie Metadaten für Ihre Tags und übergeben Sie diese an den Parameter `openapi_tags`:

{* ../../docs_src/metadata/tutorial004_py310.py hl[3:16,18] *}

    * `url` (**requerido**): un `str` con la URL para la documentación externa.

### Crear metadata para etiquetas { #create-metadata-for-tags }

Probemos eso en un ejemplo con etiquetas para `users` y `items`.

Crea metadata para tus etiquetas y pásala al parámetro `openapi_tags`:

{* ../../docs_src/metadata/tutorial004_py310.py hl[3:16,18] *}