Поэтому в этом примере мы должны объявить тип ответа в параметре `response_model`.

...но читайте дальше, чтобы узнать, как это обойти.

## Возвращаемый тип и фильтрация данных { #return-type-and-data-filtering }

Продолжим предыдущий пример. Мы хотели **аннотировать функцию одним типом**, но при этом иметь возможность вернуть из функции что-то, что фактически включает **больше данных**.

    /**
     * Returns list of file configuration settings.
     * Supports both GET and PUT requests for retrieving paginated file configuration settings.
     *
     * @param body search parameters for filtering and pagination
     * @return JSON response containing file configuration settings list with pagination info
     */
    @Execute
    public JsonResponse<ApiResult> settings(final SearchBody body) {

```

```java
extractorFactory.addExtractor("application/myformat", myExtractor, weight);
```

3. **Add test with sample file** in `src/test/resources/`

### Configuring URL Filtering

```java
// Include patterns (must match)
crawler.urlFilter.addInclude("https://example.com/.*");

// Exclude patterns (must not match)
crawler.urlFilter.addExclude(".*\\.(css|js|png|jpg)$");
```

    //                                                                      ==============
    /**
     * Displays the role management index page.
     *
     * @param form the search form for filtering
     * @return HTML response for the role list page
     */
    @Execute
    @Secured({ ROLE, ROLE + VIEW })
    public HtmlResponse index(final SearchForm form) {
        return asListHtml();
    }

    /**

 * </p>
 *
 * <p>
 * The reader supports limiting the number of documents read based on a percentage of the total documents
 * or a fixed number. It also allows filtering documents based on their size, using the {@code limitOfDocumentSize}
 * parameter.
 * </p>
 *
 * <p>
 * The reader uses a queue to buffer documents read from Elasticsearch, and it retries failed requests

 *
 * <p>Key functionalities include:</p>
 * <ul>
 *   <li>Setting the target index for the search.</li>
 *   <li>Limiting the number of results (size).</li>
 *   <li>Filtering by tags, roles, fields, and languages.</li>
 *   <li>Excluding specific words from the results.</li>
 *   <li>Building the OpenSearch query and rescorer for the popular words search.</li>

    /**
     * Returns list of elevate word settings.
     * Supports both GET and PUT requests for retrieving paginated elevate word configurations.
     *
     * @param body search parameters for filtering and pagination
     * @return JSON response containing elevate word settings list with pagination info
     */
    @Execute
    public JsonResponse<ApiResult> settings(final SearchBody body) {

                * Serialization: you could return an arbitrary object and the
                    `response_model` would be used to serialize that object into the
                    corresponding JSON.
                * Filtering: the JSON sent to the client will only contain the data
                    (fields) defined in the `response_model`. If you returned an object
                    that contains an attribute `password` but the `response_model` does

- **Crawl Sources**: URLs, file shares, databases being indexed
- **Custom Configurations**: URL patterns, security rules, metadata fields
- **Search Features**: Facets, suggestions, security filtering, ranking rules
- **Integration Points**: Applications consuming search APIs
- **User Permissions**: Access control and label configurations

### 2. Infrastructure Requirements

        // The iterator returns null when no elements, doesn't throw exception
        assertNull(iterator.next(), "Should return null when no next element");
    }

    /**
     * Test multiple iterations with mixed filtering results.
     */
    @Test
    void testMultipleIterationsWithFilter() throws Exception {
        // Given
        when(mockDelegate.hasNext()).thenReturn(true, true, true, false);