mockBhv.setTestData(testData);

        int count = relatedQueryHelper.load();
        assertEquals(1, count); // One virtual host key (empty)

        String[] results = relatedQueryHelper.getRelatedQueries("java");
        assertEquals(3, results.length);
        assertEquals("programming", results[0]);

    }

    @Test
    public void test_load_simpleTerms() {
        List<RelatedContent> testData = new ArrayList<>();
        testData.add(createRelatedContent("java", "Java Programming", ""));
        testData.add(createRelatedContent("python", "Python Programming", ""));
        mockBhv.setTestData(testData);

        int count = relatedContentHelper.load();
        assertEquals(1, count); // One virtual host key (empty)

    "Framework :: Pydantic :: 2",
    "Intended Audience :: Developers",
    "Programming Language :: Python :: 3 :: Only",
    "Programming Language :: Python :: 3.10",
    "Programming Language :: Python :: 3.11",
    "Programming Language :: Python :: 3.12",
    "Programming Language :: Python :: 3.13",
    "Programming Language :: Python :: 3.14",
    "Topic :: Internet :: WWW/HTTP :: HTTP Servers",

        // assertEquals(0, result.size()); // Commented out due to variable scope
    }

    @Test
    public void test_buildQuery_withVariousKeywords() {
        List<String> keywordList = Arrays.asList("java", "programming", "search", "");
        List<FilterFunctionBuilder> functionBuilders = new ArrayList<>();

        try {
            keyMatchHelper.buildQuery(keywordList, functionBuilders);
        } catch (Exception e) {

American English was chosen for the following reasons:

* **Current predominance**: The majority of existing Gradle code and documentation already uses American English
* **Industry standard**: Most widely used programming languages, frameworks, and tools (Java, Kotlin, JavaScript, etc.) use American English in their APIs and documentation
* **Consistency with dependencies**: Gradle's ecosystem and dependencies predominantly use American English

### French instructions about technical terms

Do not try to translate everything. In particular, keep common programming terms (e.g. `framework`, `endpoint`, `plug-in`, `payload`).

Keep class names, function names, modules, file names, and CLI commands unchanged.

### List of English terms and their preferred French translations

   *
   * <p><i>Notes:</i> This is an implementation of the algorithm for Lexicographical Permutations
   * Generation, described in Knuth's "The Art of Computer Programming", Volume 4, Chapter 7,
   * Section 7.2.1.2. The iteration order follows the lexicographical order. This means that the
   * first permutation will be in ascending order, and the last will be in descending order.
   *

## Open Source SDK Generators { #open-source-sdk-generators }

A versatile option is the [OpenAPI Generator](https://openapi-generator.tech/), which supports **many programming languages** and can generate SDKs from your OpenAPI specification.

For **TypeScript clients**, [Hey API](https://heyapi.dev/) is a purpose-built solution, providing an optimized experience for the TypeScript ecosystem.

## What is "Dependency Injection" { #what-is-dependency-injection }

**"Dependency Injection"** means, in programming, that there is a way for your code (in this case, your *path operation functions*) to declare things that it requires to work and use: "dependencies".

That's why it makes a lot of sense to use asynchronous ⏸🔀⏯ code for web APIs.

This kind of asynchronicity is what made NodeJS popular (even though NodeJS is not parallel) and that's the strength of Go as a programming language.

And that's the same level of performance you get with **FastAPI**.