referral.link = "testLink";
        referral.path = "/test/path";
        referral.ttl = 300;
        referral.expiration = 1234567890L;
        referral.resolveHashes = true;

        // When
        String expectedString =
                "DfsReferral[pathConsumed=20,server=testServer,share=testShare,link=testLink,path=/test/path,ttl=300,expiration=1234567890,resolveHashes=true]";

        }

        @Test
        @DisplayName("Test path property")
        void testPathProperty() {
            testBlock.setPath("\\new\\path");
            assertEquals("\\new\\path", testBlock.getPath());
        }

        @Test
        @DisplayName("Test full UNC path properties")
        void testFullUNCPathProperties() {

        int i = 0, b = 0;
        final int len = path.length();

        do {
            if (ri == rlast) {
                result[rlast] = path.substring(b);
                return;
            }
            if (i == len || path.charAt(i) == '\\') {
                result[ri] = path.substring(b, i);
                ri++;
                b = i + 1;
            }
        } while (i++ < len);

# Body - Множество параметров

Теперь, когда мы увидели, как использовать `Path` и `Query` параметры, давайте рассмотрим более продвинутые примеры обьявления тела запроса.

## Обьединение `Path`, `Query` и параметров тела запроса

Во-первых, конечно, вы можете объединять параметры `Path`, `Query` и объявления тела запроса в своих функциях обработки, **FastAPI** автоматически определит, что с ними нужно делать.

import org.apache.maven.api.annotations.Immutable;
import org.apache.maven.api.annotations.Nonnull;

import static org.apache.maven.api.ExtensibleEnums.pathScope;

/**
 * Path scope.
 * A path scope is used to determine the kind of build or class path that will be built when resolving
 * dependencies using the {@link org.apache.maven.api.services.DependencyResolver} service.
 * <p>

# via a symlink.
# Helpful since the internal CI utilizes a T:\ drive, part of which is mounted
# to the container, and would result in C:\<path> != T:\<path> mismatches,
# when using variables like `TFCI_OUTPUT_DIR` in `docker exec commands,
# requiring conditional path adjustments throughout the CI scripts.
# Note: This does not work for `docker cp` commands.
# For a little more detail, see:

    have prod supersource, even if they have none. GWT is happy to ignore us
    when we specify a nonexistent path.

    (I hope that this workaround does not cause its own problems in the future.)
-->
<super-source path="super"/>

<inherits name="com.google.common.annotations.Annotations" />
<inherits name="com.google.common.base.Base" />
<inherits name="com.google.common.math.Math" />

    have prod supersource, even if they have none. GWT is happy to ignore us
    when we specify a nonexistent path.

    (I hope that this workaround does not cause its own problems in the future.)
-->
<super-source path="super"/>

<inherits name="com.google.common.annotations.Annotations" />
<inherits name="com.google.common.base.Base" />

    override fun getSubprojectByName(name: String) = nameToSubproject[name]

    private fun toSubproject(subproject: Map<String, Any>): GradleSubproject {
        val name = subproject["name"] as String
        val path = subproject["path"] as String
        val unitTests = !ignoredSubprojects.contains(name) && subproject["unitTests"] as Boolean
        val functionalTests = !ignoredSubprojects.contains(name) && subproject["functionalTests"] as Boolean

 * This form is used in the admin API interface to upload files to the storage backend
 * with optional path specification for file organization.
 */
public class UploadForm {

    /**
     * The storage path where the file should be uploaded.
     * If not specified, the file will be stored in the default location.
     */
    public String path;

    /**
     * The multipart file to be uploaded to the storage system.