## Múltiples parámetros de cuerpo y query

Por supuesto, también puedes declarar parámetros adicionales de query siempre que lo necesites, además de cualquier parámetro del cuerpo.

Como, por defecto, los valores singulares se interpretan como parámetros de query, no tienes que añadir explícitamente un `Query`, solo puedes hacer:

```Python
q: Union[str, None] = None
```

        SuggestItem.Kind[] kinds1 = { SuggestItem.Kind.QUERY };
        SuggestItem.Kind[] kinds2 = { SuggestItem.Kind.DOCUMENT, SuggestItem.Kind.QUERY };

        SuggestItem.Kind[] result = SuggestItem.concatKinds(kinds1, kinds2);

        assertNotNull(result);
        assertEquals(2, result.length); // Should not have duplicates
        assertTrue(Arrays.asList(result).contains(SuggestItem.Kind.QUERY));

                        .status(ApiResult.Status.OK)
                        .result());
    }

    /**
     * Retrieves a specific related query setting by ID.
     *
     * @param id the ID of the related query to retrieve
     * @return JSON response containing the related query configuration
     */
    // GET /api/admin/relatedquery/setting/{id}
    @Execute
    public JsonResponse<ApiResult> get$setting(final String id) {

                "Unknown q: " + query.getClass() + " => " + query);
    }

    /**
     * Converts a wildcard query to an appropriate OpenSearch QueryBuilder.
     *
     * @param context The query context containing field and search information
     * @param wildcardQuery The Lucene wildcard query to convert
     * @param boost The boost factor to apply to the query
     * @return The converted OpenSearch QueryBuilder

     * The search is performed using the current virtual host context and
     * the query term is converted to lowercase for case-insensitive matching.
     *
     * @param query the search term to find related queries for
     * @return an array of related query strings, or empty array if none found
     */
    public String[] getRelatedQueries(final String query) {
        final String key = ComponentUtil.getVirtualHostHelper().getVirtualHostKey();

* Both _paths_ take `GET` operations (also known as HTTP _methods_).
* The _path_ `/items/{item_id}` has a _path parameter_ `item_id` that should be an `int`.
* The _path_ `/items/{item_id}` has an optional `str` _query parameter_ `q`.

### Interactive API docs { #interactive-api-docs }

Now go to <a href="http://127.0.0.1:8000/docs" class="external-link" target="_blank">http://127.0.0.1:8000/docs</a>.

/** File generated by Grunt -- do not modify
 *  JQUERY-FORM-VALIDATOR
 *
 *  @version 2.3.77
 *  @website http://formvalidator.net/
 *  @author Victor Jonsson, http://victorjonsson.se
 *  @license MIT
 */

     * Sets the time taken to execute the search query in milliseconds.
     *
     * @param queryTime The query execution time in milliseconds
     */
    public void setQueryTime(final long queryTime) {
        this.queryTime = queryTime;
    }

    /**
     * Sets the actual search query executed against the search engine.
     *
     * @param searchQuery The search query string
     */

///

## Modellattribute deklarieren

Dann können Sie `Field` mit Modellattributen deklarieren:

{* ../../docs_src/body_fields/tutorial001_an_py310.py hl[11:14] *}

`Field` funktioniert genauso wie `Query`, `Path` und `Body`, es hat die gleichen Parameter, usw.

/// note | Technische Details

import org.codelibs.fess.unit.UnitFessTestCase;
import org.codelibs.fess.util.ComponentUtil;
import org.dbflute.util.DfTypeUtil;
import org.opensearch.index.query.BoolQueryBuilder;
import org.opensearch.index.query.QueryBuilder;
import org.opensearch.index.query.QueryBuilders;
import org.opensearch.index.query.TermQueryBuilder;

public class BooleanQueryCommandTest extends QueryTestBase {

    private BooleanQueryCommand booleanQueryCommand;