...but continue reading below to see how to overcome that.

## Return Type and Data Filtering { #return-type-and-data-filtering }

Let's continue from the previous example. We wanted to **annotate the function with one type**, but we wanted to be able to return from the function something that actually includes **more data**.

            return getAllWebConfigList();
        }
        return getAllWebConfigList(true, true, false, idList);
    }

    /**
     * Retrieves web crawling configurations with various filtering options.
     *
     * @param withLabelType whether to include label type information (currently not used in implementation)

 */
public class UpdateLabelJob {

    private static final Logger logger = LogManager.getLogger(UpdateLabelJob.class);

    /**
     * Query builder for filtering documents to be processed.
     */
    protected QueryBuilder queryBuilder = null;

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

									<filtering>true</filtering>
									<includes>
										<include>**/*</include>
									</includes>
									<excludes>
										<exclude>packaging.properties</exclude>
									</excludes>
								</resource>
								<resource>
									<directory>src/packaging/deb/</directory>
									<filtering>true</filtering>
									<includes>
										<include>**/*</include>

    }

    /**
     * Generates URL query parameters for facet filtering.
     *
     * @return URL-encoded query string containing facet parameters
     */
    public static String facetQuery() {
        return createQuery(Constants.FACET_QUERY, FACET_PREFIX);
    }

    /**
     * Generates URL query parameters for geographic filtering.
     *

 *
 * <p>The parser handles the following GSA configuration elements:
 * <ul>
 * <li>Collections with good/bad URL patterns</li>
 * <li>Global parameters including start URLs and filtering rules</li>
 * <li>User agent settings</li>
 * <li>URL pattern matching with regular expressions and contains filters</li>
 * </ul>
 *
 */
public class GsaConfigParser extends DefaultHandler {

É por isso que neste exemplo temos que declará-lo no parâmetro `response_model`.

...mas continue lendo abaixo para ver como superar isso.

## Tipo de Retorno e Filtragem de Dados { #return-type-and-data-filtering }

Vamos continuar do exemplo anterior. Queríamos **anotar a função com um tipo**, mas queríamos poder retornar da função algo que realmente incluísse **mais dados**.

### FastAPI Datenfilterung { #fastapi-data-filtering }

FastAPI seinerseits wird den Rückgabetyp sehen und sicherstellen, dass das, was zurückgegeben wird, **nur** diejenigen Felder enthält, welche im Typ deklariert sind.

        // Default constructor
    }

    /**
     * Command-line options for the thumbnail generator.
     */
    protected static class Options {
        /**
         * Session ID for filtering thumbnail generation.
         */
        @Option(name = "-s", aliases = "--sessionId", metaVar = "sessionId", usage = "Session ID")
        protected String sessionId;

        /**

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

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

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

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