| quote }} {{- end }} secretName: {{ .secretName }} {{- end }} {{- end }} rules: {{- range .Values.consoleIngress.hosts }} - http: paths: - path: {{ $ingressPath }} {{- if semverCompare ">=1.19-0" $.Capabilities.KubeVersion.GitVersion }} pathType: Prefix backend: service: name: {{ $fullName }} port: number: {{ $servicePort }} {{- else }} backend: serviceName: {{ $fullName }} servicePort: {{ $servicePort }} {{- end }} {{- if . }} host: {{ . | quote }} {{- end }} {{- end }} {{- end }} minio/templat...

這只會在啟動時花費微秒等級，且只發生一次。

因此不會影響效能。⚡

///

### 以自訂的 `prefix`、`tags`、`responses` 與 `dependencies` 納入一個 `APIRouter` { #include-an-apirouter-with-a-custom-prefix-tags-responses-and-dependencies }

現在，假設你的組織提供了一個 `app/internal/admin.py` 檔案給你。

它包含一個帶有一些管理員路徑操作的 `APIRouter`，並在組織內多個專案之間共用。

為了這個範例它會非常簡單。但假設因為它會與組織內的其他專案共用，我們不能直接修改它並把 `prefix`、`dependencies`、`tags` 等加在 `APIRouter` 上：

Bu işlem mikrosaniyeler sürer ve sadece startup sırasında olur.

Dolayısıyla performansı etkilemez. ⚡

///

### Özel `prefix`, `tags`, `responses` ve `dependencies` ile Bir `APIRouter` Dahil Edin { #include-an-apirouter-with-a-custom-prefix-tags-responses-and-dependencies }

Şimdi, kurumunuzun size `app/internal/admin.py` dosyasını verdiğini düşünelim.

    //                                                                        ============

    /**
     * Returns the coordinator index name, adjusted for the configured index prefix.
     *
     * @return the coordinator index name.
     */
    protected String getIndexName() {
        final FessConfig fessConfig = ComponentUtil.getFessConfig();

func (s StubKMS) ListKeys(ctx context.Context, req *ListRequest) ([]madmin.KMSKeyInfo, string, error) {
	matches := []madmin.KMSKeyInfo{}
	if req.Prefix == "" {
		req.Prefix = "*"
	}
	for _, keyName := range s.KeyNames {
		if wildcard.MatchAsPatternPrefix(req.Prefix, keyName) {
			matches = append(matches, madmin.KMSKeyInfo{Name: keyName, CreatedAt: StubCreatedAt, CreatedBy: StubCreatedBy})
		}
	}

	return matches, "", nil

<img src="/img/tutorial/bigger-applications/image01.png">

## Inclure le même routeur plusieurs fois avec des `prefix` différents { #include-the-same-router-multiple-times-with-different-prefix }

Vous pouvez aussi utiliser `.include_router()` plusieurs fois avec le même routeur en utilisant des préfixes différents.

| quote }} {{- end }} secretName: {{ .secretName }} {{- end }} {{- end }} rules: {{- range .Values.consoleIngress.hosts }} - http: paths: - path: {{ $ingressPath }} {{- if semverCompare ">=1.19-0" $.Capabilities.KubeVersion.GitVersion }} pathType: Prefix backend: service: name: {{ $fullName }} port: number: {{ $servicePort }} {{- else }} backend: serviceName: {{ $fullName }} servicePort: {{ $servicePort }} {{- end }} {{- if . }} host: {{ . | quote }} {{- end }} {{- end }} {{- end }} minio/templat...

<img src="/img/tutorial/bigger-applications/image01.png">

## Inclua o mesmo router várias vezes com `prefix` diferentes { #include-the-same-router-multiple-times-with-different-prefix }

Você também pode usar `.include_router()` várias vezes com o *mesmo* router usando prefixos diferentes.

        AdminSearchlistAction.validateFields(doc, errorMessages::add);

        assertFalse(errorMessages.isEmpty());

        // Verify error messages use field names without doc. prefix
        final FessMessages messages = new FessMessages();
        errorMessages.forEach(m -> m.message(messages));

        assertTrue(messages.hasMessageOf("doc.url"));

Esto tomará microsegundos y solo sucederá al inicio.

Así que no afectará el rendimiento. ⚡

///

### Incluir un `APIRouter` con un `prefix`, `tags`, `responses`, y `dependencies` personalizados { #include-an-apirouter-with-a-custom-prefix-tags-responses-and-dependencies }

Ahora, imaginemos que tu organización te dio el archivo `app/internal/admin.py`.