```

So, when you need to declare a value as required while using `Query`, you can simply not declare a default value:

{* ../../docs_src/query_params_str_validations/tutorial006_an_py310.py hl[9] *}

### Required, can be `None` { #required-can-be-none }

You can declare that a parameter can accept `None`, but that it's still required. This would force clients to send a value, even if the value is `None`.

### Short { #short }

It has sensible **defaults** for everything, with optional configurations everywhere. All the parameters can be fine-tuned to do what you need and to define the API you need.

But by default, it all **"just works"**.

### Validation { #validation }

* Validation for most (or all?) Python **data types**, including:
    * JSON objects (`dict`).

# ADR-0002 - Avoid using Java serialization

## Status

- ACCEPTED on 2023-12-01

## Context

In Gradle we often need to serialize in-memory objects for caching, or to transmit them across process barriers, etc.
Java serialization is one way to implement this, however, despite its simplicity of implementation, it has several drawbacks:

- **Performance:**
Java's built-in serialization mechanism is often slower compared to other serialization solutions.

            LOGGER.warn("No files need to be deleted.");
            return;
        }

        final Set<File> filesToDelete = allFilesInCheckout.stream()
            .filter(each -> earlierFiles.contains(each.getName()))
            .collect(Collectors.toCollection(TreeSet::new));

        if (filesToDelete.isEmpty()) {
            LOGGER.warn("No files need to be deleted.");
            return;
        }

E.g.:

* To pass a *path* or *query* parameter, add it to the URL itself.
* To pass a JSON body, pass a Python object (e.g. a `dict`) to the parameter `json`.
* If you need to send *Form Data* instead of JSON, use the `data` parameter instead.
* To pass *headers*, use a `dict` in the `headers` parameter.
* For *cookies*, a `dict` in the `cookies` parameter.

```mermaid
sequenceDiagram
    participant App
    participant Client

    App->>App: Produce Item 1
    App->>Client: Send Item 1
    App->>App: Produce Item 2
    Client->>Client: Process Item 1
    App->>Client: Send Item 2
    App->>App: Produce Item 3
    Client->>Client: Process Item 2
    App->>Client: Send Item 3
    Client->>Client: Process Item 3
    Note over App: Keeps producing...
    Note over Client: Keeps consuming...

However, if there are no changes for more than a week, it's safe to assume that the issue is up for grabs.
There is no need to ask for an assignment or for permission to work on those issues, just comment and start working on it.

## Setting up your development environment

In order to make changes to Gradle, you'll need:

            message.setFlags(request.getFlags());
            message.setTimeout((int) (context.getConfig().getWitnessRegistrationTimeout() / 1000));

            // Send the RPC request
            rpcHandle.sendrecv(message);

            // Create response from RPC message results
            WitnessRegisterResponse response = new WitnessRegisterResponse();

  source $(dirname "${SCRIPT}")/java-versions-aarch64.properties
  export JAVA15_HOME="${HOME}"/.java/jdk15
else
  source $(dirname "${SCRIPT}")/java-versions.properties
  ## We are caching BWC versions too, need these so we can build those
  export JAVA8_HOME="${HOME}"/.java/java8
  export JAVA11_HOME="${HOME}"/.java/java11
  export JAVA12_HOME="${HOME}"/.java/openjdk12
  export JAVA13_HOME="${HOME}"/.java/openjdk13

 * and their completion status.
 */
public class RdmaWorkRequest {

    /**
     * Type of RDMA work request
     */
    public enum RequestType {
        /** Send operation */
        SEND,
        /** Receive operation */
        RECEIVE,
        /** RDMA read operation */
        READ,
        /** RDMA write operation */
        WRITE
    }

    private final long requestId;