labels.user_title_details=Utilisateur
labels.role_configuration=Rôle
labels.role_list_name=Nom
labels.role_name=Nom
labels.role_title_details=Rôle
labels.group_configuration=Groupe
labels.group_list_name=Nom
labels.group_name=Nom
labels.group_title_details=Groupe
labels.related_content_configuration=Contenu associé
labels.related_content_content=Contenu
labels.related_content_list_term=Terme
labels.related_content_term=Terme

 *
 * <p><a id="iteration"></a>
 *
 * <p><b>Key-grouped iteration.</b> All view collections follow the same iteration order. In all
 * current implementations, the iteration order always keeps multiple entries with the same key
 * together. Any creation method that would customarily respect insertion order (such as {@link
 * #copyOf(Multimap)}) instead preserves key-grouped order by inserting entries for an existing key

 *
 * <p><a id="iteration"></a>
 *
 * <p><b>Key-grouped iteration.</b> All view collections follow the same iteration order. In all
 * current implementations, the iteration order always keeps multiple entries with the same key
 * together. Any creation method that would customarily respect insertion order (such as {@link
 * #copyOf(Multimap)}) instead preserves key-grouped order by inserting entries for an existing key

     */
    @Size(max = 10)
    public String loginRequired;

    /**
     * Enable or disable result collapsing for similar documents.
     * When enabled, similar search results are grouped together.
     */
    @Size(max = 10)
    public String resultCollapsed;

    /**
     * Enable or disable display of login link in the search interface.

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:

* `ItemsService`
* `UsersService`

### Client Method Names { #client-method-names }