* Model interpolation does not give same result when calculated from build or from repo...
     * This is why MNG-5000 fix in code is marked as bad practice (uses file names)
     * @throws IOException Model read problem
     */
    @Test
    void testFlatTrickyUrls() throws IOException {
        // parent references child with artifactId (which is not directory name)

 * ListMultimap} and {@link SetMultimap}. These take their names from the fact that the collections
 * they return from {@code get} behave like (and, of course, implement) {@link List} and {@link
 * Set}, respectively.
 *
 * <p>For example, the "presidents" code snippet above used a {@code ListMultimap}; if it had used a
 * {@code SetMultimap} instead, two presidents would have vanished, and last names might or might
 * not appear in chronological order.

	iamSTSAccountsMap map[string]UserIdentity
	// map of STS access key to policy names
	iamSTSPolicyMap *xsync.MapOf[string, MappedPolicy]

	// map of group names to group info
	iamGroupsMap map[string]GroupInfo
	// map of user names to groups they are a member of
	iamUserGroupMemberships map[string]set.StringSet
	// map of group names to policy names
	iamGroupPolicyMap *xsync.MapOf[string, MappedPolicy]
}

        }

        /**
         * Gets the initialization parameter value for the given parameter name.
         *
         * This method maps SPNEGO configuration parameter names to their corresponding
         * values from system properties or default values. It handles various
         * authentication and security settings for SPNEGO.
         *

这样你就可以在客户端代码中把内容正确地组织和分组：

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

在这个例子中，你会有：

* `ItemsService`
* `UsersService`

### 客户端方法名 { #client-method-names }

现在，像 `createItemItemsPost` 这样的生成方法名看起来不太简洁：

```TypeScript
ItemsService.createItemItemsPost({name: "Plumbus", price: 5})
```

...这是因为客户端生成器会把每个*路径操作*的 OpenAPI 内部**操作 ID（operation ID）**用作方法名的一部分。

 * including authentication, authorization, and HTML data setup.
 * </p>
 *
 */
public abstract class FessAdminAction extends FessBaseAction {

    /** Constant suffix for view names. */
    public static final String VIEW = "-view";

    /**
     * Default constructor.
     */
    public FessAdminAction() {
        super();
    }

        QueryBuilder result = fuzzyQueryCommand.convertFuzzyQuery(context, fuzzyQuery, 1.0f);
        assertNotNull(result);

    }

    // Test with various field names
    @Test
    public void test_convertFuzzyQuery_withVariousFields() {
        QueryContext context = new QueryContext("test", false);
        String[] fields = { "title", "content", "url", "site", "host", "mimetype" };

### Using the *path operation function* name as the operationId { #using-the-path-operation-function-name-as-the-operationid }

If you want to use your APIs' function names as `operationId`s, you can iterate over all of them and override each *path operation's* `operation_id` using their `APIRoute.name`.

You should do it after adding all your *path operations*.

    }

    /**
     * Parses a search hit from OpenSearch and converts it to a document map.
     *
     * @param fessConfig the Fess configuration
     * @param hlPrefix the highlight prefix for field names
     * @param searchHit the search hit to parse
     * @return the parsed document as a map
     */

        assertTrue("Should have many label constants", labelConstantCount > 100);
    }

    /**
     * Test that label constant values match their field names
     */
    @Test
    public void test_labelConstantValueMatchesName() throws Exception {
        Field[] fields = FessLabels.class.getDeclaredFields();

        for (Field field : fields) {