<artifactId>modello-maven-plugin</artifactId>
        <configuration>
          <version>1.2.0</version>
          <models>
            <model>src/main/mdo/core-extensions.mdo</model>
          </models>
          <templates>
            <template>model.vm</template>
          </templates>
          <params>
            <param>locationTracking=true</param>

    /**
     * Gets the raw model to build. If not set, model source will be used to load raw model.
     *
     * @return The raw model to build or {@code null} if not set.
     */
    Model getRawModel();

    /**
     * Set raw model.
     *
     * @param rawModel
     */
    ModelBuildingRequest setRawModel(Model rawModel);

    /**
     * Gets the source of the POM to process.

## 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.

          <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>

### Modelo para Entrada { #model-for-input }

Si usas este modelo como entrada, como aquí:

{* ../../docs_src/separate_openapi_schemas/tutorial001_py310.py ln[1:15] hl[14] *}

...entonces el campo `description` **no será requerido**. Porque tiene un valor por defecto de `None`.

### Modelo de Entrada en la Documentación { #input-model-in-docs }

### Modelo para Entrada { #model-for-input }

Se você usar esse modelo como entrada, como aqui:

{* ../../docs_src/separate_openapi_schemas/tutorial001_py310.py ln[1:15] hl[14] *}

... então o campo `description` **não será obrigatório**. Porque ele tem um valor padrão de `None`.

### Modelo de Entrada na Documentação { #input-model-in-docs }

from fastapi.openapi.models import SecurityBase as SecurityBaseModel


class SecurityBase:
    model: SecurityBaseModel

    disabled = user_dict["disabled"],
    hashed_password = user_dict["hashed_password"],
)
```

/// info

For a more complete explanation of `**user_dict` check back in [the documentation for **Extra Models**](../extra-models.md#about-user-in-dict){.internal-link target=_blank}.

///

## Return the token { #return-the-token }

The response of the `token` endpoint must be a JSON object.

## 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`).

But you are not restricted to using some specific data model, class or type.

          <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>