* 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();
  }

        assertNotNull(queryBuilder3);
    }

    public void test_convertWildcardQuery_withSpecialCharacters() throws Exception {
        // Test with special wildcard characters
        QueryContext queryContext1 = new QueryContext("te?t*", false);
        WildcardQuery wildcardQuery1 = new WildcardQuery(new Term("title", "te?t*"));

        assertEquals("Zterm", manualUnicodeStringZterm.toString(), "toString should work with manually set buffer and length (with zterm)");

        // Test toString with buffer containing non-printable characters or special unicode
        String unicodeChars = "你好世界"; // "Hello World" in Chinese
        UnicodeString unicodeStringChinese = new UnicodeString(unicodeChars, false);

* declare the `q` query parameter without a `Query` nor any default value
* declare the path parameter `item_id` using `Path`
* have them in a different order
* not use `Annotated`

...Python has a little special syntax for that.

Pass `*`, as the first parameter of the function.

		{
			queryParams: map[string]string{
				"response-content-disposition": "attachment; filename=\"4K%2d4M.txt\"",
			},
			expected: ErrNone,
		},
		// (7) Should not error signature matches with no special query params.
		{
			queryParams: map[string]string{},
			expected:    ErrNone,
		},
	}

	// Run each test case individually.
	for i, testCase := range testCases {

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

            when(mockNetbiosName.getName()).thenReturn(testName);
            assertEquals(testName, mockNetbiosName.getName());
        }
    }

    @Test
    @DisplayName("Should handle special characters in names")
    void testSpecialCharacters() {
        String[] testNames = { "SERVER-1", "SERVER_A", "SRV123", "MY-SRV" };

        for (String testName : testNames) {

  internal const val OPCODE_CONTROL_PING = 0x9
  internal const val OPCODE_CONTROL_PONG = 0xa

  /**
   * Maximum length of frame payload. Larger payloads, if supported by the frame type, can use the
   * special values [PAYLOAD_SHORT] or [PAYLOAD_LONG].
   */
  internal const val PAYLOAD_BYTE_MAX = 125L

  /** Maximum length of close message in bytes. */
  internal const val CLOSE_MESSAGE_MAX = PAYLOAD_BYTE_MAX - 2

  /**