To see what exactly you can include in the responses, you can check these sections in the OpenAPI specification:

* [OpenAPI Responses Object](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.1.0.md#responses-object), it includes the `Response Object`.

			<lineEnding>unix</lineEnding>
			<includes>
				<include>fess.in.sh</include>
				<include>fess</include>
				<include>generate-thumbnail</include>
			</includes>
		</fileSet>
		<fileSet>
			<filtered>false</filtered>
			<outputDirectory>fess-${project.version}/bin</outputDirectory>
			<includes>
				<include>module.xml</include>
				<include>plugin.xml</include>
			</includes>
		</fileSet>

		<!-- lib -->

We want FastAPI to keep **filtering** the data using the response model. So that even though the function returns more data, the response will only include the fields declared in the response model.

  | grep -E -v "^//tensorflow" \
  | sed -e 's|:.*||' \
  | sort -u
}

# Verify that, given a build target and a license-list generator target, all of
# the dependencies of that target which include a license notice file are then
# included when generating that license. Necessary because the license targets
# in TensorFlow are manually enumerated rather than generated automatically.
do_external_licenses_check(){
  BUILD_TARGET="$1"

      </includes>
    </fileSet>
	<fileSet>
      <directory>src/assembly/maven/bin</directory>
      <outputDirectory>bin</outputDirectory>
      <includes>
        <include>mvn</include>
        <include>mvnenc</include>
        <include>mvnsh</include>
        <include>mvnup</include>
        <include>mvnDebug</include>
        <include>mvnencDebug</include>
        <!-- This is so that CI systems can periodically run the profiler -->

Y un response con un código de estado `200` que usa tu `response_model`, pero incluye un `example` personalizado:

{* ../../docs_src/additional_responses/tutorial003_py310.py hl[20:31] *}

Todo se combinará e incluirá en tu OpenAPI, y se mostrará en la documentación de la API:

<img src="/img/tutorial/additional-responses/image01.png">

 * ## Reactive Authentication
 *
 * Implementations authenticate by returning a follow-up request that includes an authorization
 * header, or they may decline the challenge by returning null. In this case the unauthenticated
 * response will be returned to the caller that triggered it.
 *
 * Implementations should check if the initial request already included an attempt to

 *
 * Class<?> someClass = ...;
 * for (Class<?> clazz : iterable(someClass)) {
 *     ...
 * }
 * </pre>
 * <p>
 * By default, the {@link Object} class is also included in the iteration. If you do not want to include {@link Object},
 * specify {@literal false} for the second argument of {@link #iterable(Class, boolean)} or {@link #ClassIterator(Class, boolean)}.
 * </p>
 *
 * @author koichik
 */

								<resource>
									<directory>${project.basedir}</directory>
									<filtering>true</filtering>
									<includes>
										<include>bin/fess</include>
										<include>bin/fess.in.sh</include>
										<include>bin/generate-thumbnail</include>
										<include>bin/plugin.xml</include>
									</includes>
								</resource>
							</resources>
						</configuration>
					</execution>
					<execution>

  </dependencies>
  <build>
    <resources>
      <resource>
        <directory>..</directory>
        <includes>
          <include>LICENSE</include> <!-- copied from the parent pom because I couldn't figure out a way to make combine.children="append" work -->
          <include>proguard/*</include>
        </includes>
        <targetPath>META-INF</targetPath>
      </resource>
    </resources>
    <plugins>
      <plugin>