你可以在[進階使用者指南](../advanced/index.md)中閱讀更多相關內容。

## 細節 { #details }

第一個 `"/static"` 指的是這個「子應用」要被「掛載」的子路徑。因此，任何以 `"/static"` 開頭的路徑都會由它處理。

`directory="static"` 指向包含你靜態檔案的目錄名稱。

`name="static"` 為它指定一個可供 **FastAPI** 內部使用的名稱。

以上參數都不一定要是 "`static`"，請依你的應用需求與細節調整。

## 更多資訊 { #more-info }

	CodeChallengeMethodsSupported    []string `json:"code_challenge_methods_supported,omitempty"`
}

// User represents information about user.
type User struct {
	Name    string `json:"username"`
	ID      string `json:"id"`
	Enabled bool   `json:"enabled"`
}

// Standard errors.
var (
	ErrNotImplemented     = errors.New("function not implemented")

    private static void generateJdkJarHellCheck(File projectRoot, Implementation mainImplementation) {
        DynamicType.Unloaded<?> dynamicType = new ByteBuddy()
                    .subclass(Object.class)
                    .name("org.elasticsearch.jdk.JdkJarHellCheck")
                .defineMethod("main",   void.class, Visibility.PUBLIC, Ownership.STATIC)
                .withParameters(String[].class)
                .intercept(mainImplementation)

    private TestTaskConfigurer() {}

    public static void configureTestTask(Test test, ObjectFactory objectFactory) {
        TestRerunTaskExtension extension = test.getExtensions()
            .create(TestRerunTaskExtension.NAME, TestRerunTaskExtension.class, objectFactory);
        test.doFirst(new InitTaskAction(extension));
    }

    private static RerunTestExecuter createRetryTestExecuter(Task task, TestRerunTaskExtension extension) {

* The `--node-name` flag for kubeadm now dictates the Node API object name the kubelet uses for registration, in all cases but where you might use an in-tree cloud provider. If you're not using an in-tree cloud provider, `--node-name` will set the Node API object name. If you're using an in-tree cloud provider, you MUST make `--node-name` match the name the in-tree cloud provider decides to use.

      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright {yyyy} {name of copyright owner}

   Licensed under the Apache License, Version 2.0 (the "License");

      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");

      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");

      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");

      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");