# Path Operation Advanced Configuration { #path-operation-advanced-configuration }

## OpenAPI operationId { #openapi-operationid }

/// warning

If you are not an "expert" in OpenAPI, you probably don't need this.

///

You can set the OpenAPI `operationId` to be used in your *path operation* with the parameter `operation_id`.

You would have to make sure that it is unique for each operation.

# Configuration avancée des paramètres de chemin

## ID d'opération OpenAPI

/// warning | Attention

Si vous n'êtes pas un "expert" en OpenAPI, vous n'en avez probablement pas besoin.

///

# Fortgeschrittene Konfiguration der Pfadoperation

## OpenAPI operationId

/// warning | Achtung

Wenn Sie kein „Experte“ für OpenAPI sind, brauchen Sie dies wahrscheinlich nicht.

///

Mit dem Parameter `operation_id` können Sie die OpenAPI `operationId` festlegen, die in Ihrer *Pfadoperation* verwendet werden soll.

Sie müssten sicherstellen, dass sie für jede Operation eindeutig ist.

Si abres la documentación automática de la API, tu extensión aparecerá en la parte inferior de la *path operation* específica.

<img src="/img/tutorial/path-operation-advanced-configuration/image01.png">

Y si ves el OpenAPI resultante (en `/openapi.json` en tu API), verás tu extensión como parte de la *path operation* específica también:

```JSON hl_lines="22"
{
    "openapi": "3.1.0",

Se você abrir os documentos criados automaticamente para a API, sua extensão aparecerá no final da *operação de rota* específica.

<img src="/img/tutorial/path-operation-advanced-configuration/image01.png">

E se você olhar o esquema OpenAPI resultante (na rota `/openapi.json` da sua API), você verá que a sua extensão também faz parte da *operação de rota* específica:

```JSON hl_lines="22"
{

Sebastián Ramírez <******@****.***> 1731896744 +0100

        return OptionalEntity.of(list.get(0));
    }

    /**
     * Stores a file configuration in the database.
     * This method encrypts the configuration parameters before saving and
     * performs an insert or update operation based on whether the configuration exists.
     *
     * @param fileConfig the file configuration to be stored
     */
    public void store(final FileConfig fileConfig) {

        // search

    }

    /**
     * Retrieves all file authentication configurations associated with a specific file configuration.
     *
     * @param fileConfigId the ID of the file configuration to retrieve authentications for
     * @return a list of file authentication configurations for the specified file configuration
     */
    public List<FileAuthentication> getFileAuthenticationList(final String fileConfigId) {

        return OptionalThing.empty();
    }

    /**
     * Configuration class that holds parsed configuration values for a field.
     * This class parses pipe-separated configuration values and provides methods
     * to check for specific configuration options.
     */
    public static class Config {

        /**
         * Array of parsed configuration values split by pipe character and trimmed.
         */

          <show>package</show>
        </configuration>
      </plugin>
      <!-- Disable "normal" testing, which doesn't work for GWT tests. -->
      <plugin>
        <artifactId>maven-surefire-plugin</artifactId>
        <configuration>
          <skip>true</skip>
        </configuration>
      </plugin>
      <plugin>
        <artifactId>maven-dependency-plugin</artifactId>