## FastAPI-Anwendung mit Tags { #fastapi-app-with-tags }

In vielen Fällen wird Ihre FastAPI-App größer sein und Sie werden wahrscheinlich Tags verwenden, um verschiedene Gruppen von *Pfadoperationen* zu separieren.

Zum Beispiel könnten Sie einen Abschnitt für **Items** und einen weiteren Abschnitt für **Users** haben, und diese könnten durch Tags getrennt sein:

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

## Aplicação FastAPI com Tags { #fastapi-app-with-tags }

Em muitos casos, sua aplicação FastAPI será maior, e você provavelmente usará tags para separar diferentes grupos de *operações de rota*.

Por exemplo, você poderia ter uma seção para **items** e outra seção para **users**, e elas poderiam ser separadas por tags:

{* ../../docs_src/generate_clients/tutorial002_py310.py hl[21,26,34] *}

# computes a hash of a remote repo's tag state.
# Tag definitions can come from the .hgtags file stored in
# any head of any branch, and the server protocol does not
# expose the tags directly. However, the protocol does expose
# the hashes of all the branch heads, so we can use a hash of
# all those branch names and heads as a conservative snapshot
# of the entire remote repo state, and use that as the tag sum.

///

### Utiliser vos tags { #use-your-tags }

Utilisez le paramètre `tags` avec vos *chemins d'accès* (et `APIRouter`s) pour les affecter à différents tags :

{* ../../docs_src/metadata/tutorial004_py310.py hl[21,26] *}

/// info

En savoir plus sur les tags dans [Configuration de chemins d'accès](path-operation-configuration.md#tags).

///

### Consultez les documents { #check-the-docs }

        String[] tags = new String[] { "tag1" };
        String[] roles = new String[] { "role1" };
        String[] langs = new String[] { "ja" };

        SuggestAnalyzer analyzer = suggester.settings().analyzer().new DefaultContentsAnalyzer();
        SuggestItem item = defaultContentsParser.parseSearchWords(words, readings, fields, tags, roles, 10, createDefaultReadingConverter(),

     *
     * <p>This method works by finding all git tags prior to {@param versionString} in the same minor series, and
     * examining the git tree for that tag. By doing this over each tag, it is possible to see how the contents
     * of the changelog directory changed over time.
     *
     * @param gitWrapper used to call `git`
     * @param versionString the "current" version. Does not require a tag in git.

file_path = Path("./openapi.json")
openapi_content = json.loads(file_path.read_text())

for path_data in openapi_content["paths"].values():
    for operation in path_data.values():
        tag = operation["tags"][0]
        operation_id = operation["operationId"]
        to_remove = f"{tag}-"
        new_operation_id = operation_id[len(to_remove) :]
        operation["operationId"] = new_operation_id

    - **price**: required
    - **tax**: if the item doesn't have tax, you can omit this
    - **tags**: a set of unique tag strings for this item
    """

		return
	}
	start := strings.LastIndex(s, "[")
	o.Marker = s[:start]
	end := strings.LastIndex(s, "]")
	tag := strings.Trim(s[start:end], "[]")
	tags := strings.SplitSeq(tag, ",")
	for tag := range tags {
		kv := strings.Split(tag, ":")
		if len(kv) < 2 {
			continue
		}
		switch kv[0] {
		case "minio_cache":
			if kv[1] != markerTagVersion {
				continue
			}

        assertTrue(ex.getMessage().contains("Invalid field in kerberos ticket"));
    }

    @Test
    @DisplayName("seq ctor: tag 3 with wrong tag class is rejected")
    void sequenceConstructor_ticketTag_wrongClass_throws() {
        // Arrange: minimal valid fields + tag 3 as CONTEXT-SPECIFIC instead of APPLICATION
        ASN1EncodableVector v = new ASN1EncodableVector();