form.crudMode = CrudMode.CREATE;
            });
        });
    }

    /**
     * Displays the form for editing an existing related content item.
     *
     * @param form the edit form containing the ID of the item to edit
     * @return HTML response for the edit form
     */
    @Execute
    @Secured({ ROLE })
    public HtmlResponse edit(final EditForm form) {

                                            <c:forEach var="p" varStatus="s"
                                                       items="${pager.pageNumberList}">
                                                <li
                                                        <c:if test="${p == pager.currentPageNumber}">class="page-item active"</c:if>>
                                                    <la:link

}

/* search */

:first-child.list-group-item {
	border-radius: 0px;
}

:last-child.list-group-item {
	border-radius: 0px;
}

#result ol li {
	margin: 1em 0;
}

#result ol li:first-child {
	margin-top: 0;
}

#result .title a:visited {
	color: #014c8c;
}

#result .body {
	display: flex;
	align-items: flex-start;
}

#result .site cite {

Open your browser at <a href="http://127.0.0.1:8000/items/5?q=somequery" class="external-link" target="_blank">http://127.0.0.1:8000/items/5?q=somequery</a>.

You will see the JSON response as:

```JSON
{"item_id": 5, "q": "somequery"}
```

You already created an API that:

* Receives HTTP requests in the _paths_ `/` and `/items/{item_id}`.

    }

    /**
     * Registers available web configuration items for use in web authentication forms.
     * Retrieves all web configurations and creates form items from them.
     *
     * @param data the render data to register the web configuration items with
     */
    protected void registerWebConfigItems(final RenderData data) {

                                                   styleClass="form-control">
                                            <c:forEach var="item" items="${protocolSchemeItems}">
                                                <la:option value="${f:u(item.value)}">${f:h(item.label)}</la:option>
                                            </c:forEach>
                                        </la:select>

    //                                               Details
    //                                               -------
    /**
     * Displays the details of a role item.
     *
     * @param crudMode the CRUD mode for the operation
     * @param id the ID of the role item to display
     * @return HTML response for the details page
     */
    @Execute
    @Secured({ ROLE, ROLE + VIEW })

## FastAPI App with Tags { #fastapi-app-with-tags }

In many cases, your FastAPI app will be bigger, and you will probably use tags to separate different groups of *path operations*.

For example, you could have a section for **items** and another section for **users**, and they could be separated by tags:

{* ../../docs_src/generate_clients/tutorial002_py39.py hl[21,26,34] *}

3. El dataclass `Author` incluye una lista de dataclasses `Item`.

4. El dataclass `Author` se usa como el parámetro `response_model`.

5. Puedes usar otras anotaciones de tipos estándar con dataclasses como el request body.

    En este caso, es una lista de dataclasses `Item`.

6. Aquí estamos regresando un diccionario que contiene `items`, que es una lista de dataclasses.

3. A dataclass `Author` inclui uma lista de dataclasses `Item`.

4. A dataclass `Author` é usada como o parâmetro `response_model`.

5. Você pode usar outras anotações de tipo padrão com dataclasses como o corpo da requisição.

    Neste caso, é uma lista de dataclasses `Item`.

6. Aqui estamos retornando um dicionário que contém `items`, que é uma lista de dataclasses.