Since before **JSON Schema** supported `examples` OpenAPI had support for a different field also called `examples`.

This **OpenAPI-specific** `examples` goes in another section in the OpenAPI specification. It goes in the **details for each *path operation***, not inside each JSON Schema.

And Swagger UI has supported this particular `examples` field for a while. So, you can use it to **show** different **examples in the docs UI**.

        dictionaryItem.id = Long.MIN_VALUE;
        assertEquals(Long.MIN_VALUE, dictionaryItem.getId());
    }

    @Test
    public void test_multipleInstances() {
        // Test that different instances have independent ID values
        TestDictionaryItem item1 = new TestDictionaryItem();
        TestDictionaryItem item2 = new TestDictionaryItem();

        item1.id = 100L;
        item2.id = 200L;

    Property<String> getSomeProperty()
}
class Example {
    Property<NestedType> getNestedProperty()
}
```

This is unnecessary because users will have trouble creating instances of `NestedType` and merging different instances of `NestedType`. It's also more awkward for users to access the properties in the nested property.

If the nested type is a managed type (Gradle can generate its implementation), you can define a nested property with:
```

            when(parent.getLocator()).thenReturn(locator);
            when(locator.getURL()).thenReturn(new URL("file:/"));
            // Throw CIFSException with different cause
            CIFSException differentException = new CIFSException("different error");
            when(locator.getAddress()).thenThrow(differentException);

            // Act + Assert

 *   <li>{@link org.apache.maven.cling.invoker.mvnup.goals.Help} - Displays usage information</li>
 * </ul>
 *
 * <h3>Upgrade Strategies</h3>
 * <p>The tool uses a strategy pattern to handle different types of upgrades:</p>
 * <ul>
 *   <li>{@link org.apache.maven.cling.invoker.mvnup.goals.ModelUpgradeStrategy} - Upgrades POM model versions (4.0.0 → 4.1.0)</li>

 * things like environment, system properties, extensions etc. are loaded only once. It is caller duty to ensure
 * that subsequent call is right for the resident instance (ie no env change or different extension needed).
 * This implementation "pre-populates" MavenContext with pre-existing stuff (except for very first call)
 * and does not let DI container to be closed.
 */

                """
                A `list` of `dict`s with connectivity information to a target server.

                You would use it, for example, if your application is served from
                different domains and you want to use the same Swagger UI in the
                browser to interact with each of them (instead of having multiple
                browser tabs open). Or if you want to leave fixed the possible URLs.

   * that this method will return a different number of chars than would be returned by reading all
   * of the chars.
   *
   * <p>Additionally, for mutable sources such as {@code StringBuilder}s, a subsequent read may
   * return a different number of chars if the contents are changed.
   *
   * @since 19.0
   */
  public Optional<Long> lengthIfKnown() {

///

## About "Form Fields" { #about-form-fields }

The way HTML forms (`<form></form>`) sends the data to the server normally uses a "special" encoding for that data, it's different from JSON.

**FastAPI** will make sure to read that data from the right place instead of JSON.

/// note | Technical Details

// compression and checksumming which currently necessitates mutating data in
// the kernel.
//
// DirectIO semantics for a filesystem like ZFS would be quite different than
// the semantics on filesystems like XFS, and these semantics are not
// implemented at this time.
// For more information on why typical DirectIO semantics do not apply to ZFS
// see this ZFS-on-Linux commit message: