* multimap. Keys and values appear in the same order as in this multimap.
   */
  @Override
  @SuppressWarnings("unchecked") // a widening cast
  public ImmutableMap<K, Collection<V>> asMap() {
    return (ImmutableMap) map;
  }

  @Override
  Map<K, Collection<V>> createAsMap() {
    throw new AssertionError("should never be called");
  }

    protected void validate(C context) throws Exception {
        if (context.invokerRequest.parsingFailed()) {
            // in case of parser errors: report errors and bail out; invokerRequest contents may be incomplete
            // in case of mvnsh the context.logger != context.invokerRequest.parserRequest.logger
            List<Logger.Entry> entries =

In some special use cases (probably not very common), you might want to **restrict** the cookies that you want to receive.

Your API now has the power to control its own <abbr title="This is a joke, just in case. It has nothing to do with cookie consents, but it's funny that even the API can now reject the poor cookies. Have a cookie. 🍪">cookie consent</abbr>. 🤪🍪

You can use Pydantic's model configuration to `forbid` any `extra` fields:

Por ejemplo, no puedes poner un modelo de Pydantic en un `JSONResponse` sin primero convertirlo a un `dict` con todos los tipos de datos (como `datetime`, `UUID`, etc.) convertidos a tipos compatibles con JSON.

Para esos casos, puedes usar el `jsonable_encoder` para convertir tus datos antes de pasarlos a un response:

{* ../../docs_src/response_directly/tutorial001_py310.py hl[5:6,20:21] *}

/// note | Detalles técnicos

 * methods of the delegate. For example, overriding {@link #add} alone <b>will not</b> change the
 * behavior of {@link #addAll}, which can lead to unexpected behavior. In this case, you should
 * override {@code addAll} as well, either providing your own implementation, or delegating to the
 * provided {@code standardAddAll} method.
 *

       *
       * ...except that it's possible for users to insert a string key with a non-string value, and
       * in that case, getProperty *will* return null.
       *
       * TODO(b/192002623): Handle that case: Either:
       *
       * - Skip non-string keys and values entirely, as proposed in the linked bug.
       *

       *
       * ...except that it's possible for users to insert a string key with a non-string value, and
       * in that case, getProperty *will* return null.
       *
       * TODO(b/192002623): Handle that case: Either:
       *
       * - Skip non-string keys and values entirely, as proposed in the linked bug.
       *

        extractor.getText(in, null);

        assertTrue("Should be called after getText", extractor.isValidateCalled());
    }

    /**
     * Test validateInputStream with edge case: empty stream.
     */
    public void test_validateInputStream_acceptsEmptyStream() {
        final InputStream emptyStream = new ByteArrayInputStream(new byte[0]);

        verifyNoInteractions(mockDir);
    }

    /**
     * Edge: name-based filter behavior for diverse inputs.
     */
    @ParameterizedTest
    @DisplayName("name-based filter matches .txt case-insensitively")
    @CsvSource({ "notes.txt,true", "REPORT.TXT,true", "image.png,false", "archive.tar.gz,false", "txt,false" })
    void nameBasedFilterTxt(String name, boolean expected) throws Exception {

        assertFalse(Arrays.equals(signingKey1, signingKey2),
                "Different preauth values should produce different derived keys for SMB 3.1.1");
    }

    @Test
    @DisplayName("Should handle edge case with all zero session key")
    void testDeriveKeys_AllZeroSessionKey() {
        // Given
        byte[] zeroSessionKey = new byte[16]; // All zeros
        int dialect = Smb2Constants.SMB2_DIALECT_0311;