<img src="/img/tutorial/generate-clients/image02.png">

你也會對要送出的有效載荷獲得自動完成：

<img src="/img/tutorial/generate-clients/image03.png">

/// tip

注意 `name` 與 `price` 的自動完成，這是由 FastAPI 應用中的 `Item` 模型所定義。

///

你在送出的資料上也會看到行內錯誤：

<img src="/img/tutorial/generate-clients/image04.png">

回應物件同樣有自動完成：

<img src="/img/tutorial/generate-clients/image05.png">

<img src="/img/tutorial/generate-clients/image02.png">

要发送的载荷也会有自动补全：

<img src="/img/tutorial/generate-clients/image03.png">

/// tip | 提示

请注意 `name` 和 `price` 的自动补全，它们是在 FastAPI 应用中的 `Item` 模型里定义的。

///

你发送的数据如果不符合要求，会在编辑器中显示内联错误：

<img src="/img/tutorial/generate-clients/image04.png">

响应对象同样有自动补全：

<img src="/img/tutorial/generate-clients/image05.png">

		"http://localhost:8080/auth/realms/minio/.well-known/openid-configuration",
		"OpenID discovery document endpoint")
	flag.StringVar(&clientID, "cid", "", "Client ID")
	flag.StringVar(&clientSec, "csec", "", "Client Secret")
	flag.StringVar(&clientScopes, "cscopes", "openid", "Client Scopes")
	flag.IntVar(&port, "port", 8080, "Port")
}

func implicitFlowURL(c oauth2.Config, state string) string {
	var buf bytes.Buffer

### Generate a TypeScript Client with Tags { #generate-a-typescript-client-with-tags }

If you generate a client for a FastAPI app using tags, it will normally also separate the client code based on the tags.

This way, you will be able to have things ordered and grouped correctly for the client code:

<img src="/img/tutorial/generate-clients/image06.png">

In this case, you have:

/// tip | 豆知識

FastAPI アプリの `Item` モデルで定義した `name` と `price` に補完が効いている点に注目してください。

///

送信データに対するインラインエラーも表示されます:

<img src="/img/tutorial/generate-clients/image04.png">

レスポンスオブジェクトにも補完があります:

<img src="/img/tutorial/generate-clients/image05.png">

## タグ付きの FastAPI アプリ { #fastapi-app-with-tags }

実運用ではアプリは大きくなり、*path operation* のグループ分けにタグを使うことが多いでしょう。

type CoreDNS struct {
	domainNames []string
	domainIPs   set.StringSet
	domainPort  string
	prefixPath  string
	etcdClient  *clientv3.Client
}

// EtcdOption - functional options pattern style
type EtcdOption func(*CoreDNS)

// DomainNames set a list of domain names used by this CoreDNS
// client setting, note this will fail if set to empty when
// constructor initializes.
func DomainNames(domainNames []string) EtcdOption {

            for (final CrawlerClient client : clientMap.values()) {
                client.setInitParameterMap(params);
            }
        }
    }

    /**
     * Sets the client map.
     * @param clientMap The map of clients.
     */
    public void setClientMap(final Map<Pattern, CrawlerClient> clientMap) {
        this.clientMap = clientMap;
    }

    /**

Bag Attributes
    friendlyName: test-client
    localKeyID: 54 69 6D 65 20 31 36 31 30 35 34 37 32 31 38 33 33 39 
Key Attributes: <No Attributes>
-----BEGIN ENCRYPTED PRIVATE KEY-----
MIIFHDBOBgkqhkiG9w0BBQ0wQTApBgkqhkiG9w0BBQwwHAQIV/BaQuOROI8CAggA
MAwGCCqGSIb3DQIJBQAwFAYIKoZIhvcNAwcECDimqPUDaqRVBIIEyBNPeVp351IS
v8s0Jscjmh/PkXe6Zb4etlvhOMbTrLdsUiXYaPaX+pwNDo61D3LR3UTz1Yt9MaIM
hgbClVQo2WhEIywJcaloEccxZ2mkP0ZWGVvm3NqfGD5ruevRxra9fvrQcpr81Sro

* Adicionar um **JSON Schema** para a resposta, na *operação de rota* do OpenAPI.
    * Isso será usado pela **documentação automática**.
    * Também será usado por ferramentas de geração automática de código do cliente.

4. Import the node certificate in the client's keystore:
   `keytool -import -alias test-node -keystore test-client.jks -storepass keypass -file test-node.crt -noprompt`
5. Export the client's certificate:
   `keytool -export -alias test-client -keystore test-client.jks -storepass keypass -file test-client.crt`
6. Import the client certificate in the node's keystore: