StopwordsItem item3 = new StopwordsItem(-1, "word3");
        assertEquals(-1, item3.getId());
    }

    @Test
    public void test_createMode() {
        // Test special behavior when id is 0 (create mode)
        StopwordsItem createItem = new StopwordsItem(0, "newword");
        assertTrue(createItem.isUpdated());
        assertEquals("newword", createItem.getNewInput());

import com.google.common.base.Function;
import java.util.concurrent.Executor;
import org.jspecify.annotations.Nullable;

/**
 * Hidden superclass of {@link FluentFuture} that provides us a place to declare special GWT
 * versions of the {@link FluentFuture#catching(Class, com.google.common.base.Function)
 * FluentFuture.catching} family of methods. Those versions have slightly different signatures.
 */

Historically, Gradle has shipped with some Groovy types in very prominent APIs.
This required the Kotlin DSL to add special integration to work with Groovy closures.
This has also forced plugins written in languages other than Groovy to use Groovy types for some APIs.

        bb.putShort((short) 22); // specialNameOffset
        bb.putShort((short) 3); // numExpanded
        bb.putShort((short) 44); // expandedNameOffset

        // Special name at offset 22
        bb.position(22);
        String specialName = "SPECIAL";
        bb.put(specialName.getBytes(StandardCharsets.UTF_16LE));
        bb.putShort((short) 0);

        // Expanded names at offset 44
        bb.position(44);

import com.google.common.base.Function;
import java.util.concurrent.Executor;
import org.jspecify.annotations.Nullable;

/**
 * Hidden superclass of {@link Futures} that provides us a place to declare special GWT versions of
 * the {@link Futures#catching(ListenableFuture, Class, com.google.common.base.Function)
 * Futures.catching} family of methods. Those versions have slightly different signatures.
 */

        assertEquals("", user.getName());

        // Test with null name
        user = new TestFessUser(null, new String[] {}, new String[] {}, new String[] {});
        assertNull(user.getName());

        // Test with special characters in name
        user = new TestFessUser("******@****.***", new String[] {}, new String[] {}, new String[] {});
        assertEquals("******@****.***", user.getName());

        // Test with Unicode characters

@app.get("/items/stream-mixed", response_class=EventSourceResponse)
async def sse_items_mixed() -> AsyncIterable[Item]:
    yield items[0]
    yield ServerSentEvent(data="custom-event", event="special")
    yield items[1]


@app.get("/items/stream-string", response_class=EventSourceResponse)
async def sse_items_string():
    yield ServerSentEvent(data="plain text data")

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

## Forbid Extra Query Parameters { #forbid-extra-query-parameters }

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

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

  // For each xxxEscaper() method, please add links to external reference pages
  // that are considered authoritative for the behavior of that escaper.

  /**
   * Returns an {@link Escaper} instance that escapes special characters in a string so it can
   * safely be included in an XML document as element content. See section <a
   * href="http://www.w3.org/TR/2008/REC-xml-20081126/#syntax">2.4</a> of the XML specification.
   *

You can verify it in the docs UI at `/docs`:

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

## Forbid Extra Form Fields { #forbid-extra-form-fields }

In some special use cases (probably not very common), you might want to **restrict** the form fields to only those declared in the Pydantic model. And **forbid** any **extra** fields.

/// note