// MS-SWN RPC Operation Numbers
    /** WitnessRegister operation number */
    public static final int WITNESS_REGISTER = 0;
    /** WitnessUnregister operation number */
    public static final int WITNESS_UNREGISTER = 1;
    /** WitnessAsyncNotify operation number */
    public static final int WITNESS_ASYNC_NOTIFY = 2;
    /** Witness heartbeat operation number */

            Doc(
                """
                Custom operation ID to be used by this *path operation*.

                By default, it is generated automatically.

                If you provide a custom operation ID, you need to make sure it is
                unique for the whole API.

                You can customize the
                operation ID generation with the parameter

   *
   * @throws UnsupportedOperationException if this range set does not support the {@code add}
   *     operation
   */
  void add(Range<C> range);

  /**
   * Removes the specified range from this {@code RangeSet} (optional operation). After this
   * operation, if {@code range.contains(c)}, {@code this.contains(c)} will return {@code false}.
   *
   * <p>If {@code range} is empty, this is a no-op.

            logger.warn("Failed to check existing operation: operation={}", operationName, e);
        }
        return false;
    }

    /**
     * Releases the operation lock by deleting the operation document.
     * Safe to call multiple times; does nothing if the document is already deleted.
     *
     * @param operationName the operation name whose lock should be released.
     */

participant dep_func as Dep scope="function"
participant operation as Path Operation

    client ->> dep_req: Start request
    Note over dep_req: Run code up to yield
    dep_req ->> dep_func: Pass dependency
    Note over dep_func: Run code up to yield
    dep_func ->> operation: Run path operation with dependency
    operation ->> dep_func: Return from path operation
    Note over dep_func: Run code after yield

        return false;
    }

    /**
     * Execute an RDMA operation with automatic retry and error handling
     *
     * @param <T> the type of result returned by the operation
     * @param operation the operation to execute
     * @param connection the RDMA connection to use
     * @return operation result
     * @throws IOException if operation fails after all retries
     */

            Doc(
                """
                Custom operation ID to be used by this *path operation*.

                By default, it is generated automatically.

                If you provide a custom operation ID, you need to make sure it is
                unique for the whole API.

                You can customize the
                operation ID generation with the parameter

It is just a function that can take all the same parameters that a *path operation function* can take:

{* ../../docs_src/dependencies/tutorial001_an_py310.py hl[8:9] *}

That's it.

**2 lines**.

And it has the same shape and structure that all your *path operation functions* have.

You can think of it as a *path operation function* without the "decorator" (without the `@app.get("/some-path")`).

Similar to the way you can [add `dependencies` to the *path operation decorators*](dependencies-in-path-operation-decorators.md), you can add them to the `FastAPI` application.

In that case, they will be applied to all the *path operations* in the application:

{* ../../docs_src/dependencies/tutorial012_an_py310.py hl[17] *}

```

...that's because the client generator uses the OpenAPI internal **operation ID** for each *path operation*.

OpenAPI requires that each operation ID is unique across all the *path operations*, so FastAPI uses the **function name**, the **path**, and the **HTTP method/operation** to generate that operation ID, because that way it can make sure that the operation IDs are unique.

But I'll show you how to improve that next. 🤓