*/
    public void setQuery(final String query) {
        this.query = query;
    }

    /**
     * Adds a tag to filter by.
     * @param tag The tag.
     */
    public void addTag(final String tag) {
        tags.add(tag);
    }

    /**
     * Adds a role to filter by.
     * @param role The role.
     */
    public void addRole(final String role) {

  # any targets in ignored packages. Combine this list of targets into a bazel
  # query list (e.g. the list becomes "target+target2+target3")
  bazel cquery --keep_going 'kind(py_test, //tensorflow/python/...) - attr("tags", "no_pip|manual", //tensorflow/python/...)' | grep -v -f $BATS_TEST_TMPDIR/ignore_deps_for_these_packages | paste -sd "+" - > $BATS_TEST_TMPDIR/deps
  # Find all one-step dependencies of those tests which are from //tensorflow

# Number of fragments for query highlighting.
query.highlight.number.of.fragments=2
# Type of query highlighting.
query.highlight.type=fvh
# Tag to use before highlighted text.
query.highlight.tag.pre=<strong>
# Tag to use after highlighted text.
query.highlight.tag.post=</strong>
# Boundary characters for query highlighting.
query.highlight.boundary.chars=u0009u000Au0013u0020
# Maximum scan for query highlight boundaries.

## 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){.internal-link target=_blank}.

servers:
  - url: http://localhost:8080/api/v1
tags:
  - name: search
    description: Search operations
  - name: popularword
    description: Popular word operations
  - name: monitor
    description: Monitoring operations
  - name: suggest
    description: Suggest operations
  - name: favorite
    description: Favorite operations
paths:
  /documents:
    get:
      tags:
        - search

So, in our example, we can make `tags` be specifically a "list of strings":

{* ../../docs_src/body_nested_models/tutorial002_py310.py hl[12] *}

## Set types { #set-types }

But then we think about it, and realize that tags shouldn't repeat, they would probably be unique strings.

And Python has a special data type for sets of unique items, the `set`.

Then we can declare `tags` as a set of strings:

 *
 * <p>Usage example:</p>
 * <pre>
 * {@code
 * DefaultContentsParser parser = new DefaultContentsParser();
 * SuggestItem item = parser.parseSearchWords(words, readings, fields, tags, roles, score, readingConverter, normalizer, analyzer, langs);
 * }
 * </pre>
 *
 * @see ContentsParser
 * @see SuggestItem
 * @see ReadingConverter
 * @see Normalizer
 * @see SuggestAnalyzer
 */

Отже, у нашому прикладі, ми можемо зробити `tags` саме "списком рядків":

{* ../../docs_src/body_nested_models/tutorial002_py310.py hl[12] *}

## Типи множин

Але потім ми подумали, що теги не повинні повторюватися, вони, ймовірно, повинні бути унікальними рядками.

І Python має спеціальний тип даних для множин унікальних елементів — це `set`.

Тому ми можемо оголосити `tags` як множину рядків:

    /**
     * Creates a new PrunedTag instance with the specified tag name.
     *
     * @param tag the HTML tag name to match (e.g., "div", "span", "p")
     */
    public PrunedTag(final String tag) {
        this.tag = tag;
    }

    /**
     * Checks if this pruned tag configuration matches the given DOM node.
     * The matching is based on tag name, and optionally ID, CSS class, or custom attributes.
     *

<hoge:address xmlns:hoge="http://www.example.com/hoge">
	<hoge:item sex="male" custid="A12345">
		<hoge:name>鈴木太郎</hoge:name>
		<hoge:access kind="email"></hoge:access>
		<hoge:access kind="url">http://www.taro.com/</hoge:access>
		<hoge:image file="taro.png" />
	</hoge:item>
	<hoge:item sex="male" custid="B23456">
		<hoge:name>佐藤二朗</hoge:name>
		<hoge:access kind="email">******@****.***</hoge:access>
		<hoge:image file="jiro.png" />
	</hoge:item>