assertTrue(npe2.getMessage().contains("non-null"));
        verifyNoInteractions(mockDir);
    }

    /**
     * Sanity: implementing via an anonymous class works the same as a lambda.
     */
    @Test
    @DisplayName("anonymous class implementation behaves correctly")
    void anonymousClassImplementation() throws Exception {
        SmbFilenameFilter filter = new SmbFilenameFilter() {

///

## Advanced User Guide { #advanced-user-guide }

There is also an **Advanced User Guide** that you can read later after this **Tutorial - User guide**.

The **Advanced User Guide** builds on this one, uses the same concepts, and teaches you some extra features.

But you should first read the **Tutorial - User Guide** (what you are reading right now).

    calls++

    if (exchange != null) {
      check(exchange.finder.routePlanner.sameHostAndPort(request.url)) {
        "network interceptor ${interceptors[index - 1]} must retain the same host and port"
      }
      check(calls == 1) {
        "network interceptor ${interceptors[index - 1]} must call proceed() exactly once"
      }
    }

    // Call the next interceptor in the chain.

   * would be the right tool for the job here: {@code @Nullable} is the annotation that we're trying
   * to get rid of, and {@code @NonNull} would be wrong for our use case for the same reason as
   * {@code requireNonNull}: Our use case is the one in which {@code T} has parametric nullness—and
   * thus its value may be legitimately {@code null}.)
   */
  @ParametricNullness
  @SuppressWarnings("nullness")

        // When
        String[] messages = NtStatus.NT_STATUS_MESSAGES;

        // Then
        assertNotNull(messages);
        assertTrue(messages.length > 0);
        // Should have same length as codes array
        assertEquals(NtStatus.NT_STATUS_CODES.length, messages.length);

        // First message should be for success
        assertNotNull(messages[0]);

/// note

This is supported since FastAPI version `0.115.0`. 🤓

///

/// tip

This same technique applies to `Query`, `Cookie`, and `Header`. 😎

///

## Cookies with a Pydantic Model { #cookies-with-a-pydantic-model }

 |                 -t /path/to/user/toolchains.xml
 |
 |  2. Installation Level.
 |                 This toolchains.xml file provides configuration for all Maven
 |                 users on a machine (assuming they're all using the same Maven
 |                 installation). It's normally provided in
 |                 ${maven.installation.conf}/toolchains.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |

## 1. Prerequisites

* Familiarity with [Docker Compose](https://docs.docker.com/compose/overview/).

You can set `schema_extra` with a `dict` containing any additional data you would like to show up in the generated JSON Schema, including `examples`.

////

/// tip

You could use the same technique to extend the JSON Schema and add your own custom extra info.

For example you could use it to add metadata for a frontend user interface, etc.

///

/// info

    public OptionalEntity<WebConfig> getWebConfig(final String id) {
        return webConfigBhv.selectByPK(id);
    }

    /**
     * Gets a web configuration by its name.
     * If multiple configurations have the same name, returns the first one ordered by sort order.
     *
     * @param name The name of the web configuration
     * @return Optional containing the web configuration if found
     */