]
}
```

/// info

Notice how the `images` key now has a list of image objects.

///

## Deeply nested models { #deeply-nested-models }

You can define arbitrarily deeply nested models:

{* ../../docs_src/body_nested_models/tutorial007_py310.py hl[7,12,18,21,25] *}

/// info

Notice how `Offer` has a list of `Item`s, which in turn have an optional list of `Image`s

///

                "Method com.example.Task.setSourceCompatibility(java.lang.String): Is not binary compatible. Reason for accepting this: Upgraded property" to listOf("Method has been removed"),

The correct place is:

* In the key `content`, that has as value another JSON object (`dict`) that contains:
    * A key with the media type, e.g. `application/json`, that contains as value another JSON object, that contains:
        * A key `schema`, that has as the value the JSON Schema from the model, here's the correct place.

        }

        fun assertHasNoError() {
            assertTrue("Has no error (${richReport.errors})", richReport.errors.isEmpty())
        }

        fun assertHasNoWarning() {
            assertTrue("Has no warning (${richReport.warnings})", richReport.warnings.isEmpty())
        }

        fun assertHasNoInformation() {
            assertTrue("Has no information (${richReport.information})", richReport.information.isEmpty())

                "item_id": "foo",
                "description": "This is an amazing item that has a long description",
            },
        ),
        (
            "/items/bar?q=somequery",
            {
                "item_id": "bar",
                "q": "somequery",
                "description": "This is an amazing item that has a long description",
            },
        ),
        (
            "/items/baz?short=true",

#### `HeroCreate` - the *data model* to create a hero { #herocreate-the-data-model-to-create-a-hero }

Now we create a `HeroCreate` model, this is the one that will **validate** the data from the clients.

It has the same fields as `HeroBase`, and it also has `secret_name`.

Now, when the clients **create a new hero**, they will send the `secret_name`, it will be stored in the database, but those secret names won't be returned in the API to the clients.

        /**
         * Sets the finished flag to indicate whether the process has completed.
         * @param finished True if the process has finished, false otherwise.
         */
        public void setFinished(final boolean finished) {
            this.finished = finished;
        }

        /**
         * Checks if the process has been terminated due to timeout.

const (
	HasOne    RelationshipType = "has_one"      // HasOneRel has one relationship
	HasMany   RelationshipType = "has_many"     // HasManyRel has many relationship
	BelongsTo RelationshipType = "belongs_to"   // BelongsToRel belongs to relationship
	Many2Many RelationshipType = "many_to_many" // Many2ManyRel many to many relationship
	has       RelationshipType = "has"
)

type Relationships struct {
	HasOne    []*Relationship

                "description": "This is an amazing item that has a long description",
            },
        ),
        (
            "/users/1/items/bar?q=somequery",
            {
                "item_id": "bar",
                "owner_id": 1,
                "q": "somequery",
                "description": "This is an amazing item that has a long description",
            },
        ),
        (

    /**
     * Array of new input character sequences for update operations.
     * When not null, indicates this item has pending updates.
     */
    private String[] newInputs;

    /**
     * The new output character sequence for update operations.
     * When not null, indicates this item has pending updates.
     */
    private String newOutput;

    /**