assertEquals(Integer.valueOf(expire), provider.provideDefaultExpire());
        }
    }

    // Test with different path values
    @Test
    public void test_differentPathValues() {
        String[] testPaths = { "/", "/app", "/test/path", "/a/b/c/d", "" };

        for (String path : testPaths) {
            ComponentUtil.setFessConfig(new FessConfig.SimpleImpl() {

        this.rootLocator = rootLocator;
        return this;
    }

    /**
     * Interpolates given {@code path}.
     *
     * @return absolute path or {@code null} if the input was {@code null}
     */
    public String interpolate(String path, ProfileActivationContext context) throws InterpolationException {
        if (path == null) {
            return null;
        }

# to `docker exec` commands, e.g., 'T:\path', instead of 'C:\path',
# without having to replace the drive letter with C:\ every time.
# Such a workaround is not required on Linux, since it
# can create arbitrary paths within the container, e.g., '/t'.
# Note: This does not affect/work for `docker cp` commands.
RUN New-Item -ItemType directory -Path C:\drive_t; \

     */
    public DictionaryFile<? extends DictionaryItem> create(final String path, final Date timestamp) {
        if (!isTarget(path)) {
            return null;
        }

        return newDictionaryFile(encodePath(path), path, timestamp);
    }

    /**
     * Encodes a file path using Base64 URL-safe encoding.
     *
     * @param path the file path to encode

        )

    private
    fun visitClassDirectory(dir: Path, classes: ClassGraph, classesDir: File, manifest: Path, buildReceipt: Path) {
        Files.walkFileTree(
            dir,
            object : FileVisitor<Path> {

                private
                var seenManifest: Boolean = false

                override fun preVisitDirectory(dir: Path?, attrs: BasicFileAttributes?) =
                    FileVisitResult.CONTINUE

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")`).

And it can return anything you want.

                });
    }

    /**
     * Flush cached writes for a file path
     *
     * @param path file path
     */
    private void flushCachedWrites(String path) {
        log.debug("Flushing cached writes for path: {}", path);

        WeakReference<SmbFile> ref = fileCache.get(path);
        if (ref != null) {
            SmbFile file = ref.get();
            if (file != null) {

    }


@pytest.mark.parametrize(
    "path",
    ["/optional-list-str", "/model-optional-list-str"],
)
def test_optional_list_str_missing(path: str):
    client = TestClient(app)
    response = client.post(path)
    assert response.status_code == 200, response.text
    assert response.json() == {"p": None}


@pytest.mark.parametrize(
    "path",
    ["/optional-list-str", "/model-optional-list-str"],
)

    /**
     * Types of path (class-path, module-path, …) where the dependency can be placed.
     * For most deterministic builds, the array length should be 1. In such case,
     * the dependency will be unconditionally placed on the specified type of path
     * and no heuristic rule will be involved.
     *
     * <p>It is nevertheless common to specify two or more types of path. For example,

        // Should allow whitelisted path
        String allowed = validator.validatePath("\\share\\allowed\\file.txt");
        assertEquals("\\share\\allowed\\file.txt", allowed);

        // Should block non-whitelisted path
        try {
            validator.validatePath("\\share\\other\\file.txt");
            fail("Should block non-whitelisted path");
        } catch (SmbException e) {