Puedes verificarlo en la interfaz de documentación en `/docs`:

<div class="screenshot">
<img src="/img/tutorial/request-form-models/image01.png">
</div>

## Prohibir Campos de Formulario Extra

En algunos casos de uso especiales (probablemente no muy comunes), podrías querer **restringir** los campos de formulario a solo aquellos declarados en el modelo de Pydantic. Y **prohibir** cualquier campo **extra**.

/// note | Nota

    }

    @Test
    @DisplayName("readPacketType with special stream returning -1 should return -1")
    void testReadPacketTypeSpecialStream() throws IOException {
        // Create a mock stream that returns exactly -1 on first read (special case)
        when(mockInputStream.read(any(byte[].class), anyInt(), anyInt())).thenReturn(-1); // Immediate EOF

    }

    /**
     * Test name with special characters
     */
    public void test_name_specialCharacters() {
        // Test with spaces
        testTransformer.setName("name with spaces");
        assertEquals("name with spaces", testTransformer.getName());

        // Test with special characters
        testTransformer.setName("name-with_special.chars#123");

        assertEquals(240000, exception.getMessage().length());
    }

    /**
     * Test constructor with special characters in message
     */
    public void test_constructor_withSpecialCharactersInMessage() {
        String message = "Error: \n\t\r\0\b\f with special chars #@!$%^&*()[]{}";
        CrawlerSystemException exception = new CrawlerSystemException(message);

        assertNotNull(exception);

     * we can override it in our non-null-guaranteeing subtypes to present a better signature to
     * their users.
     *
     * However, the checker *we* use has this special knowledge about `Collection.toArray()` anyway,
     * so in our implementation code, we can rely on that. That's why the expression below
     * type-checks.
     */
    return super.toArray();
  }

  open fun contentLength(): Long = -1L

  /** Writes the content of this request to [sink]. */
  @Throws(IOException::class)
  abstract fun writeTo(sink: BufferedSink)

  /**
   * A duplex request body is special in how it is **transmitted** on the network and
   * in the **API contract** between OkHttp and the application.
   *
   * This method returns false unless it is overridden by a subclass.
   *
   * ### Duplex Transmission

        assertEquals(unicodeFileName, decodedName);
        assertEquals(20 + nameLength, bytesWritten);
    }

    @Test
    @DisplayName("Test with special characters in filename")
    void testWithSpecialCharactersInFilename() throws SMBProtocolDecodingException {
        String specialFileName = "file!@#$%^&*().txt";

<div class="screenshot">
<img src="/img/tutorial/query-param-models/image01.png">
</div>

## Restrinja Parâmetros de Consulta Extras

Em alguns casos especiais (provavelmente não muito comuns), você queira **restrinjir** os parâmetros de consulta que deseja receber.

Você pode usar a configuração do modelo Pydantic para `forbid` (proibir) qualquer campo `extra`:

Você pode verificar na UI de documentação em `/docs`:

<div class="screenshot">
<img src="/img/tutorial/request-form-models/image01.png">
</div>

## Proibir Campos Extras de Formulários

Em alguns casos de uso especiais (provavelmente não muito comum), você pode desejar **restringir** os campos do formulário para aceitar apenas os declarados no modelo Pydantic. E **proibir** qualquer campo **extra**.

/// note | Nota

        // Assert
        assertNotNull(result);
        assertTrue(result.contains("TransWaitNamedPipe"));
        assertTrue(result.contains("pipeName=null"));
    }

    @Test
    @DisplayName("toString with special characters in pipe name")
    void testToStringWithSpecialCharacters() {
        // Arrange
        String specialPipeName = "\\PIPE\\test$pipe#123";