child.project.url.inherit.append.path="false">
  <modelVersion>4.0.0</modelVersion>

  <groupId>inheritance</groupId>
  <artifactId>parent</artifactId>
  <version>11-SNAPSHOT</version>

  <name>Model urls inheritance test parent, with special merge test for mergeSite_ChildSiteUrlInheritAppendPath</name>

  <scm child.scm.connection.inherit.append.path="false"
       child.scm.developerConnection.inherit.append.path="false"

    <artifactId>parent</artifactId>
    <version>11-SNAPSHOT</version>
  </parent>

  <groupId>inheritance</groupId>
  <artifactId>inheritance</artifactId>
  <version>11-SNAPSHOT</version>
  <name>Model urls inheritance test child</name>

  <scm child.scm.connection.inherit.append.path="true"
       child.scm.developerConnection.inherit.append.path="true"
       child.scm.url.inherit.append.path="true">

{* ../../docs_src/response_change_status_code/tutorial001_py310.py hl[1,9,12] *}

And then you can return any object you need, as you normally would (a `dict`, a database model, etc).

And if you declared a `response_model`, it will still be used to filter and convert the object you returned.

...このレスポンスでは次のように返されます:

```json
{
  "message": "Hello World"
}
```

もちろん、JSONの整形以外にも、これを活用するもっと良い方法が見つかるはずです。 😉

### `orjson` か レスポンスモデルか { #orjson-or-response-model }

もし求めているのがパフォーマンスであれば、`orjson` レスポンスを使うより、[レスポンスモデル](../tutorial/response-model.md) を使うほうが良い場合が多いです。

レスポンスモデルがあると、FastAPI は中間ステップ（他の場合に行われる `jsonable_encoder` による変換など）を介さずに、Pydantic を使ってデータをJSONにシリアライズします。

{* ../../docs_src/response_headers/tutorial002_py310.py hl[1, 7:8] *}

Ensuite, vous pouvez renvoyer n'importe quel objet dont vous avez besoin, comme d'habitude (un `dict`, un modèle de base de données, etc.).

Et si vous avez déclaré un `response_model`, il sera toujours utilisé pour filtrer et convertir l'objet que vous avez renvoyé.

 * under the License.
 */
package org.apache.maven.settings.validation;

import org.apache.maven.settings.Settings;
import org.apache.maven.settings.building.SettingsProblemCollector;

/**
 * Validate a model settings
 *
 * @deprecated since 4.0.0, use {@code org.apache.maven.impl.DefaultSettingsValidator} instead
 */
@Deprecated(since = "4.0.0")
public interface SettingsValidator {

    /**

 * under the License.
 */
package org.apache.maven.toolchain.io;

import java.io.IOException;
import java.io.Writer;
import java.util.Map;

import org.apache.maven.toolchain.model.PersistedToolchains;

/**
 * Handles serialization of toolchains into some kind of textual format like XML.
 *
 * @deprecated since 4.0.0, use {@code org.apache.maven.api.services.xml.ToolchainsXmlFactory} instead
 */

    <artifactId>parent</artifactId>
    <version>11-SNAPSHOT</version>
  </parent>

  <groupId>inheritance</groupId>
  <artifactId>inheritance</artifactId>
  <version>11-SNAPSHOT</version>
  <name>Model urls inheritance test child</name>

  <scm child.scm.connection.inherit.append.path="false"
       child.scm.developerConnection.inherit.append.path="false"
       child.scm.url.inherit.append.path="false">

  child.project.url.inherit.append.path="false">
  <modelVersion>4.0.0</modelVersion>

  <groupId>inheritance</groupId>
  <artifactId>parent</artifactId>
  <version>11-SNAPSHOT</version>

  <name>Model urls inheritance test parent, with special merge test for mergeSite_ChildSiteUrlInheritAppendPath</name>

  <scm child.scm.connection.inherit.append.path="false"
       child.scm.developerConnection.inherit.append.path="false"

  <groupId>inheritance</groupId>
  <artifactId>parent</artifactId>
  <version>11-SNAPSHOT</version>

  <name>Model urls inheritance test parent</name>
  <description>Flat directory structure case: module = ../child-artifact-id + child directory path != child-artifact-id</description>

  <modules>
    <module>../child-artifact-id</module><!-- use child artifact id, even if different from directory -->
  </modules>