}

    /**
     * Creates a path prefix with trailing slash if path is not empty.
     *
     * @param path the base path
     * @return path with trailing slash or empty string
     */
    protected static String getPathPrefix(final String path) {
        return StringUtil.isEmpty(path) ? StringUtil.EMPTY : path + "/";
    }

    /**
     * Combines path and name to create a full object name.
     *

		wantRes string
		wantKey string
		wantVal string
		ok      bool
	}{
		{"6 k=v\n\n", "\n", "k", "v", true},
		{"19 path=/etc/hosts\n", "", "path", "/etc/hosts", true},
		{"210 path=" + longName + "\nabc", "abc", "path", longName, true},
		{"110 path=" + medName + "\n", "", "path", medName, true},
		{"9 foo=ba\n", "", "foo", "ba", true},
		{"11 foo=bar\n\x00", "\x00", "foo", "bar", true},

ItemsService.createItemItemsPost({name: "Plumbus", price: 5})
```

...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.

    private final ThreadLocal<Path> fileThreadLocal = new ThreadLocal<>();

    Path createFile() throws IOException {
      Path file = java.nio.file.Files.createTempFile("SinkSourceFile", "txt");
      fileThreadLocal.set(file);
      return file;
    }

    Path getPath() {
      return fileThreadLocal.get();
    }

```

...eso es porque el generador del cliente usa el **operation ID** interno de OpenAPI para cada *path operation*.

OpenAPI requiere que cada operation ID sea único a través de todas las *path operations*, por lo que FastAPI usa el **nombre de la función**, el **path**, y el **método/operación HTTP** para generar ese operation ID, porque de esa manera puede asegurarse de que los operation IDs sean únicos.

          args: >
            --no-progress --offline '**/*.md' --include-fragments
            --exclude-path 'platforms/documentation/docs/src/docs/release/notes.md'
            --exclude-path 'platforms/documentation/docs/src/docs/release/notes-template.md'
            --exclude-path 'platforms/documentation/docs/src/docs/kotlin/Module.md'

<!DOCTYPE components PUBLIC "-//DBFLUTE//DTD LastaDi 1.0//EN"
	"http://dbflute.org/meta/lastadi10.dtd">
<components>
	<include path="convention.xml" />
	<include path="lastaflute_core.xml"/>
	<include path="fess.xml" />

	<include path="crawler_opensearch.xml" />
	<include path="fess_thumbnail.xml" />
	<include path="fess_ingest.xml" />

	<component name="labelTypeHelper" class="org.codelibs.fess.helper.LabelTypeHelper">
	</component>

    private int treeFlags;
    private final String path;

    /**
     * Creates a new SMB2 tree connect request to establish a connection to a network share.
     *
     * @param config the CIFS configuration
     * @param path the UNC path to the share to connect to
     */
    public Smb2TreeConnectRequest(final Configuration config, final String path) {
        super(config, SMB2_TREE_CONNECT);
        this.path = path;

## Multiple path and query parameters { #multiple-path-and-query-parameters }

You can declare multiple path parameters and query parameters at the same time, **FastAPI** knows which is which.

And you don't have to declare them in any specific order.

They will be detected by name:

    }

    // Happy path: transport is returned and verified
    @Test
    @DisplayName("getTransport returns mocked transport")
    void getTransport_happy() {
        when(session.getTransport()).thenReturn(transport);
        assertSame(transport, session.getTransport());
        verify(session).getTransport();
    }

    // Happy path: connect to logon share completes without exception
    @Test