*       module path, but is also compatible with placement on the class path. Compatibility can
     *       be achieved, for example, by repeating in the {@code META-INF/services/} directory the services
     *       that are declared in the {@code module-info.class} file. In that case, the path type can be chosen
     *       by the plugin.</li>
     *   <li>If a {@link #patchModule(String)} is also set and the main JAR file is placed on the module path,

    public void testMethodOverrides() throws NoSuchMethodException {
        // Given
        Class<?> clazz = SmbComTreeDisconnect.class;

        // When & Then - verify methods are declared in this class (overridden)
        Method writeParameterWords = clazz.getDeclaredMethod("writeParameterWordsWireFormat", byte[].class, int.class);
        assertNotNull(writeParameterWords);

   * font/woff} to be the correct media type for WOFF, but this may be necessary in certain
   * situations for compatibility.
   *
   * @since 17.0
   */
  public static final MediaType WOFF = createConstant(APPLICATION_TYPE, "font-woff");

  /**
   * <a href="https://tools.ietf.org/html/rfc8081">RFC 8081</a> declares {@link #FONT_WOFF2

Next it will convert and validate the data. So, when you use that `settings` object, you will have data of the types you declared (e.g. `items_per_user` will be an `int`).

### Use the `settings` { #use-the-settings }

Then you can use the new `settings` object in your application:

{* ../../docs_src/settings/tutorial001.py hl[18:20] *}

    }

    /**
     * Test all fields are public and accessible
     */
    @Test
    @DisplayName("Test all fields are public")
    public void testAllFieldsArePublic() {
        // Get all declared fields
        Field[] fields = ServerData.class.getDeclaredFields();

        // Verify we have the expected number of fields
        assertEquals(19, fields.length);

        // Verify all fields are public

It will include all the routes from that router as part of it.

/// note | Technical Details

It will actually internally create a *path operation* for each *path operation* that was declared in the `APIRouter`.

So, behind the scenes, it will actually work as if everything was the same single app.

///

/// check

You don't have to worry about performance when including routers.

   * font/woff} to be the correct media type for WOFF, but this may be necessary in certain
   * situations for compatibility.
   *
   * @since 17.0
   */
  public static final MediaType WOFF = createConstant(APPLICATION_TYPE, "font-woff");

  /**
   * <a href="https://tools.ietf.org/html/rfc8081">RFC 8081</a> declares {@link #FONT_WOFF2

         * annotations in the form of JetBrains annotations, which have only class retention and
         * thus are invisible at runtime. Thus, we conclude that the parameter types are
         * *non*-nullable, even when they are declared as `Foo?`.
         */
        || hasAutomaticNullChecksFromKotlin(member);
  }

  private static boolean hasAutomaticNullChecksFromKotlin(Member member) {

    * If it is not, the client will see a useful, clear error.
* Check if there is an optional query parameter named `q` (as in `http://127.0.0.1:8000/items/foo?q=somequery`) for `GET` requests.
    * As the `q` parameter is declared with `= None`, it is optional.
    * Without the `None` it would be required (as is the body in the case with `PUT`).
* For `PUT` requests to `/items/{item_id}`, read the body as JSON:

          <version>1.0.0+</version>
          <type>String</type>
          <required>true</required>
          <description>
            The name of the parameter, to be used while configuring this parameter from the Mojo's declared defaults
            or from the POM.
          </description>
        </field>
        <field>
          <name>alias</name>
          <version>1.0.0+</version>
          <type>String</type>