t.Fatalf("Should find 3 tags")
	}

	DB.Model(&blog2).Association("SharedTags").Find(&tags)
	if !compareTags(tags, []string{"tag1", "tag2", "tag3", "tag4"}) {
		t.Fatalf("Should find 3 tags")
	}

	// Replace
	tag5 := &Tag{Locale: "ZH", Value: "tag5"}
	tag6 := &Tag{Locale: "ZH", Value: "tag6"}
	DB.Model(&blog2).Association("SharedTags").Replace(tag5, tag6)
	var tags2 []Tag

        tags = PrunedTag.parse("a.test");
        assertEquals(1, tags.length);
        assertEquals("PrunedTag [tag=a, id=null, css=test, attrName=null, attrValue=null]", tags[0].toString());

        tags = PrunedTag.parse("a[target=_blank]");
        assertEquals(1, tags.length);
        assertEquals("PrunedTag [tag=a, id=null, css=null, attrName=target, attrValue=_blank]", tags[0].toString());

        String[] tags1 = { "tag1", "tag2" };
        String[] tags2 = { "tag2", "tag1" };
        String[] roles = { "role1" };
        String[] fields = { "field1" };
        String[] excludes = { "exclude1" };

        String result1 = popularWordHelper.getCacheKey(seed, tags1, roles, fields, excludes);
        String result2 = popularWordHelper.getCacheKey(seed, tags2, roles, fields, excludes);

## Metadata for tags { #metadata-for-tags }

You can also add additional metadata for the different tags used to group your path operations with the parameter `openapi_tags`.

It takes a list containing one dictionary for each tag.

Each dictionary can contain:

* `name` (**required**): a `str` with the same tag name you use in the `tags` parameter in your *path operations* and `APIRouter`s.

    }

    /**
     * Gets the custom pre-tags for highlighting.
     *
     * @return the pre-tags array, or null if using defaults
     */
    public String[] getPreTags() {
        return preTags;
    }

    /**
     * Sets the custom pre-tags for highlighting with fluent interface.
     *
     * @param preTags the pre-tags to set
     * @return this HighlightInfo instance for method chaining

									<div class="form-group row">
										<div class="col-sm-6">
											<input type="text" id="tags.${f:h(nameKey)}" name="tags.${f:h(nameKey)}" value="${f:h(savedTags.get(nameKey))}" class="form-control" placeholder="Name" >
										</div>
										<div class="col-sm-6">
											<input type="text" id="tags.${f:h(valueKey)}" name="tags.${f:h(valueKey)}" value="${f:h(savedTags.get(valueKey))}" class="form-control" placeholder="Value" >

            "lastname": "Sanchez",
            "age": "70",
            "tags": ["plumbus", "citadel"],
            "with": "something",
        },
    )
    assert response.status_code == 200, response.text
    assert response.json() == {
        "username": "Rick",
        "lastname": "Sanchez",
        "age": 70,
        "tags": ["plumbus", "citadel"],
        "with": "something",
    }

<img src="/img/tutorial/path-operation-configuration/image01.png">

### Tags with Enums { #tags-with-enums }

If you have a big application, you might end up accumulating **several tags**, and you would want to make sure you always use the **same tag** for related *path operations*.

In these cases, it could make sense to store the tags in an `Enum`.

**FastAPI** supports that the same way as with plain strings:

### 建立標籤的中繼資料 { #create-metadata-for-tags }

我們用 `users` 與 `items` 兩個標籤來示範。

先為你的標籤建立中繼資料，然後將它傳給 `openapi_tags` 參數：

{* ../../docs_src/metadata/tutorial004_py310.py hl[3:16,18] *}

注意你可以在描述中使用 Markdown，例如「login」會以粗體（**login**）顯示，而「fancy」會以斜體（_fancy_）顯示。

/// tip | 提示

你不必為你使用到的每個標籤都加入中繼資料。

///

### 使用你的標籤 { #use-your-tags }

在你的路徑操作（以及 `APIRouter`s）上使用 `tags` 參數，將它們歸類到不同標籤下：

## Documentation Tags - OpenAPI { #documentation-tags-openapi }

To add tags to your *path operations*, and group them in the docs UI, read the docs for [Tutorial - Path Operation Configurations - Tags](../tutorial/path-operation-configuration.md#tags).

## Documentation Summary and Description - OpenAPI { #documentation-summary-and-description-openapi }