}
        searchRenderData.setDocumentItems(documents);

        searchRenderData.setSearchQuery("complex search query");
        searchRenderData.setQueryTime(150L);
        searchRenderData.setExecTime("0.15 sec");
        searchRenderData.setRequestedTime(System.currentTimeMillis());
        searchRenderData.setQueryId("complex-query-id");
        searchRenderData.setAppendHighlightParams("&hl=true&hl.fl=title,content");

- Is small, focused, and easy to review—ideally one commit, unless multiple commits better narrate complex work.
- Adheres to MinIO’s coding standards (e.g., Go style, error handling, testing).

PRs must flow smoothly through review to reach production. Large PRs should be split into smaller, manageable ones.

## Submitting PRs

* Valider des **structures complexes** :
    * Utilisation de modèles Pydantic hiérarchiques, de `List` et `Dict` du `typing` Python, etc.
    * Et les validateurs permettent de définir, vérifier et documenter clairement et facilement des schémas de données complexes en tant que JSON Schema.

        } catch (final Exception e) {
            fail("Initialize should not throw exception with valid annotation: " + e.getMessage());
        }
    }

    // Test parameter validation without relying on complex configuration
    @Test
    public void test_validateParameters_basic() {
        // Test that parameter validation can be performed
        final CustomSize validAnnotation = createBasicAnnotation();

        try {

It is quite an extensive specification and covers several complex use cases.

It includes ways to authenticate using a "third party".

That's what all the systems with "login with Facebook, Google, X (Twitter), GitHub" use underneath.

### OAuth 1 { #oauth-1 }

There was an OAuth 1, which is very different from OAuth2, and more complex, as it included direct specifications on how to encrypt the communication.

                WebResourceRoot.class.isAssignableFrom(FessWebResourceRoot.class));
    }

    @Test
    public void test_classStructure() {
        // Basic class structure tests that don't require complex mocking
        assertEquals("FessWebResourceRoot should be in correct package", "org.codelibs.fess.tomcat.webresources.FessWebResourceRoot",
                FessWebResourceRoot.class.getName());

        assertEquals(originalQueryName, extractedQueryName);
    }

    @Test
    public void test_complex_field_names() {
        // Test various complex field names
        String[] fieldNames = { "simple_field", "field-with-dashes", "field.with.dots", "field_with_underscores", "fieldWithCamelCase",

        RenderData data = new RenderData();

        ComplexObject obj = new ComplexObject();
        obj.setValue("complex value");

        RenderDataUtil.register(data, "complex", obj);

        Object result = data.getDataMap().get("complex");
        assertEquals(obj, result); // Non-entity objects are registered as-is
    }

    @Test
    public void test_register_arrayList() {

5. The daemon sends the result back. For some requests, this might be a simple success/failure result, and for others this might also include a more complex object, such as a tooling API model.

    /**
     * This test primarily exists to ensure the constants interface can be loaded
     * and to provide a basic check of its values.
     * Since it's an interface with only static final fields, there is no complex logic to test.
     */
    @Test
    void testConstants() {
        // A simple assertion to verify that some of the constants have the expected values.