} catch (final NoSuchFieldException e) {
            throw new NoSuchFieldRuntimeException(clazz, name, e);
        }
    }

    /**
     * Returns a {@link Field} object that reflects the specified declared field of the class or interface represented by the {@link Class} object.
     *
     * @param clazz
     *            The {@link Class} object representing the class. Must not be {@literal null}.
     * @param name

Si no se especifica y la dependencia tiene `yield`, tendrá un `scope` de `"request"` por defecto.

### `scope` para sub-dependencias { #scope-for-sub-dependencies }

Cuando declaras una dependencia con `scope="request"` (el valor por defecto), cualquier sub-dependencia también necesita tener un `scope` de `"request"`.

If you go to `/docs`, you will see that it has the **schemas** for the data to be sent in requests and received in responses:

<img src="/img/tutorial/generate-clients/image01.png">

You can see those schemas because they were declared with the models in the app.

That information is available in the app's **OpenAPI schema**, and then shown in the API docs.

    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);

        fw.println("#");
        fw.println("# The checker does not handle implicit section names, so they must be explicit and declared as: [[section-name]]");
        fw.println("#");
        fw.println("# The checker also rejects Markdown-style links, such as [text](https://example.com/something) as they do not render properly");

    }

Se não for especificado e a dependência tiver `yield`, ela terá `scope` igual a `"request"` por padrão.

### `scope` para subdependências { #scope-for-sub-dependencies }

Quando você declara uma dependência com `scope="request"` (o padrão), qualquer subdependência também precisa ter `scope` igual a `"request"`.

            assertNotNull(e.getCause());
            assertTrue(e.getCause() instanceof IllegalArgumentException);
        }
    }

    /**
     * Test exception in method that declares throws
     */
    public void test_exceptionInMethod() {
        try {
            methodThatThrowsException();
            fail("Should have thrown CrawlerSystemException");

  and this will lead to counter-intuitive results. A different feature may exist
  unimplemented, which is to detect when the network is down and provide better
  feedback for that case. However, when offline mode is declared, nothing
  earmarked as remote should be accessed, regardless of whether it is actually
  a physically local resource.

  NOTE: One side effect of this design change is that all offline-mode code can

///

### Criar o objeto `Settings` { #create-the-settings-object }

Importe `BaseSettings` do Pydantic e crie uma subclasse, muito parecido com um modelo do Pydantic.

Da mesma forma que com modelos do Pydantic, você declara atributos de classe com anotações de tipo e, possivelmente, valores padrão.

    }

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