"name": "The Baz"
        }
    ]
}
```

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

Apart from all the fancy words used here, the **Dependency Injection** system is quite simple.

Just functions that look the same as the *path operation functions*.

But still, it is very powerful, and allows you to declare arbitrarily deeply nested dependency "graphs" (trees).

/// tip

All this might not seem as useful with these simple examples.

But you will see how useful it is in the chapters about **security**.

<a href="https://zuplo.link/fastapi-gh" target="_blank" title="Zuplo: Deploy, Secure, Document, and Monetize your FastAPI"><img src="https://fastapi.tiangolo.com/img/sponsors/zuplo.png"></a>
<a href="https://liblab.com?utm_source=fastapi" target="_blank" title="liblab - Generate SDKs from FastAPI"><img src="https://fastapi.tiangolo.com/img/sponsors/liblab.png"></a>

        assertEquals(longMessage, exception.getMessage());
        assertNull(exception.getCause());
    }

    public void test_getCause_withNestedExceptions() {
        // Test deeply nested exception causes
        Exception level3 = new Exception("Level 3: Database connection failed");
        Exception level2 = new Exception("Level 2: User lookup failed", level3);

* Editor support, including:
    * Completion.
    * Type checks.
* Validation of data:
    * Automatic and clear errors when the data is invalid.
    * Validation even for deeply nested JSON objects.
* <abbr title="also known as: serialization, parsing, marshalling">Conversion</abbr> of input data: coming from the network to Python data and types. Reading from:
    * JSON.
    * Path parameters.

        assertEquals("original2", retrievedValues[1]);

        // Modify retrieved array
        retrievedValues[0] = "modified1";

        // Verify the parameter's values can still be modified (not deeply immutable)
        assertEquals("modified1", param.getValues()[0]);

        // This shows that the class returns the same array reference
        assertSame(retrievedValues, param.getValues());
    }

            assertTrue(result.contains("NullPointerException"));
            assertTrue(result.contains("\n"));
        }

        @Test
        @DisplayName("Should handle deeply nested exceptions")
        void testToStringWithNestedExceptions() {
            Exception innermost = new IOException("Innermost exception");
            Exception middle = new RuntimeException("Middle exception", innermost);

            System.clearProperty(Constants.FESS_CONFIG_PREFIX + arrayKey);
        }
    }

    // Test property key with dots
    public void test_get_propertyKeyWithDots() {
        String dottedKey = "deeply.nested.property.key";
        String dottedValue = "nested-value";

        System.setProperty(Constants.FESS_CONFIG_PREFIX + dottedKey, dottedValue);

        try {

            }
        }
    }
}
```

### Custom OpenAPI *path operation* schema { #custom-openapi-path-operation-schema }

The dictionary in `openapi_extra` will be deeply merged with the automatically generated OpenAPI schema for the *path operation*.

So, you could add additional data to the automatically generated schema.

 *       collection. Undefined behavior and bugs will result. It's generally best to avoid using
 *       mutable objects as elements at all, as many users may expect your "immutable" object to be
 *       <i>deeply</i> immutable.
 * </ul>
 *
 * <h4>Performance notes</h4>
 *
 * <ul>
 *   <li>Implementations can be generally assumed to prioritize memory efficiency, then speed of