Você pode usar o atributo `model_config`, que recebe um `dict`, conforme descrito na [documentação do Pydantic: Configuration](https://docs.pydantic.dev/latest/api/config/).

Você pode definir `"json_schema_extra"` com um `dict` contendo quaisquer dados adicionais que você queira que apareçam no JSON Schema gerado, incluindo `examples`.

        assertNull(info.query);
        assertNull(info.size);
        assertNull(info.minDocCount);
        assertNull(info.sort);
        assertNull(info.missing);
    }

    // Test init method with various configurations
    @Test
    public void test_init_withAllFields() {
        FessConfig fessConfig = new FessConfig.SimpleImpl() {
            @Override
            public String getQueryFacetFields() {

        labelTypeHelper.load();

        Set<String> result = labelTypeHelper.getMatchedLabelValueSet("/test/path");
        assertNotNull(result);
        // Result depends on test data configuration
    }

    // Helper method to create test data
    private List<LabelType> createTestLabelTypeList() {
        List<LabelType> labelTypeList = new ArrayList<>();

/**
 * Tests for the scheduler start API endpoint contract.
 * Verifies that {@code PUT /api/admin/scheduler/{id}/start} returns the correct
 * {@code jobLogId} based on the job's logging configuration.
 */
public class ApiAdminSchedulerActionTest extends UnitFessTestCase {

    @Override
    protected boolean isUseOneTimeContainer() {
        return true;
    }

    @Override

        assertEquals("/login/newpassword.jsp", FessHtmlPath.path_Login_NewpasswordJsp.getRoutingPath());
    }

    @Test
    public void test_configPaths() throws Exception {
        // Test configuration paths
        assertEquals("/admin/webconfig/admin_webconfig.jsp", FessHtmlPath.path_AdminWebconfig_AdminWebconfigJsp.getRoutingPath());

			lifecycleResponse:  []byte(``),
			errorResponse: APIErrorResponse{
				Resource: SlashSeparator + bucketName + SlashSeparator,
				Code:     "NoSuchLifecycleConfiguration",
				Message:  "The lifecycle configuration does not exist",
			},
			shouldPass: false,
		},
	}

	testBucketLifecycle(obj, instanceType, bucketName, apiRouter, t, testCases)
}

        assertNotNull(newInstance);

        // Verify default values work for new instance
        assertEquals("warm", newInstance.getLastaDiSmartDeployMode());
    }

    // Test edge cases for mail configuration
    public void xtest_mailConfiguration_edgeCases() {
        // Test with empty host and port
        FessEnv.SimpleImpl emptyMailEnv = new FessEnv.SimpleImpl() {
            protected Properties prepareProperties() {

Where the spec is ambiguous, OkHttp follows modern user agents such as popular Browsers or common HTTP Libraries.

OkHttp is principled and avoids being overly configurable, especially when such configuration is
to workaround a buggy server, test invalid scenarios or that contradict the relevant RFC.
Other HTTP libraries exist that fill that gap allowing extensive customisation including potentially
invalid requests.

Handlers should remain backwards compatible. If a breaking API change is required, a new handler ID should be created.

## Setup & Configuration

A **Manager** is used to manage all incoming and outgoing connections to a server.

On startup all remote servers must be specified.
From that individual connections will be spawned to each remote server,

    /** Factory for creating ingesters to process documents */
    private IngestFactory ingestFactory = null;

    /**
     * Initializes the callback implementation after dependency injection.
     * Sets up configuration values and initializes the ingest factory if available.
     */
    @PostConstruct
    public void init() {
        if (logger.isDebugEnabled()) {