"input": "XL",
            }
        ],
        "body": {"title": "towel", "size": "XL"},
    }


def test_post():
    data = {"title": "towel", "size": 5}
    response = client.post("/items/", json=data)
    assert response.status_code == 200, response.text
    assert response.json() == data


def test_openapi_schema():

We are not restricted to having only one dependency that can return that type of data.

///

## Other models { #other-models }

You can now get the current user directly in the *path operation functions* and deal with the security mechanisms at the **Dependency Injection** level, using `Depends`.

And you can use any model or data for the security requirements (in this case, a Pydantic model `User`).

            <goals>
              <goal>velocity</goal>
            </goals>
            <configuration>
              <version>4.0.0</version>
              <models>
                <model>target/mdo/maven.mdo</model>
              </models>
              <templates>
                <template>src/main/mdo/model-v3.vm</template>
                <template>src/main/mdo/merger.vm</template>

          <basedir>${project.basedir}/../../api/maven-api-toolchain</basedir>
          <velocityBasedir>${project.basedir}/../../src/mdo</velocityBasedir>
          <models>
            <model>src/main/mdo/toolchains.mdo</model>
          </models>
        </configuration>
        <executions>
          <execution>
            <id>velocity</id>
            <goals>
              <goal>velocity</goal>
            </goals>

## Use Case { #use-case }

Let's start with an example **use case** and then see how to solve it with this.

Let's imagine that you have some **machine learning models** that you want to use to handle requests. 🤖

The same models are shared among requests, so, it's not one model per request, or one per user or something similar.

import static eu.maveniverse.domtrip.maven.MavenPomElements.ModelVersions.MODEL_VERSION_4_1_0;

/**
 * Strategy for applying Maven inference optimizations.
 * For 4.0.0 models: applies limited inference (parent-related only).
 * For 4.1.0+ models: applies full inference optimizations.
 * Removes redundant information that can be inferred by Maven during model building.
 */
@Named
@Singleton
@Priority(30)

 */
@Deprecated(since = "4.0.0")
public interface ModelBuildingResult {

    /**
     * Gets the sequence of model identifiers that denote the lineage of models from which the effective model was
     * constructed. Model identifiers have the form {@code <groupId>:<artifactId>:<version>}. The first identifier from

          <basedir>${project.basedir}/../../api/maven-api-settings</basedir>
          <velocityBasedir>${project.basedir}/../../src/mdo</velocityBasedir>
          <models>
            <model>src/main/mdo/settings.mdo</model>
          </models>
          <params>
            <param>forcedIOModelVersion=1.2.0</param>
            <param>packageModelV3=org.apache.maven.settings</param>

 * minimum element-set for a valid project pom


Maven super model

 Inheritance is recursive in Maven but there is a special model which is the implicit super parent in the lineage
 of models you may specify:

 all of the models that you specify are collected to produce a lineage and then the super model is place at
 the top of that lineage to provide default values.

from fastapi.openapi.models import SecurityBase as SecurityBaseModel


class SecurityBase:
    model: SecurityBaseModel