assertEquals("SERVER2", serverList.get(1).oemDomainName);
    }

    /**
     * Test field types match expected types
     */
    @Test
    @DisplayName("Test field types are correct")
    public void testFieldTypes() throws NoSuchFieldException {
        // Verify field types
        assertEquals(byte.class, ServerData.class.getDeclaredField("sflags").getType());

@app.post("/items/")
async def create_items(items: ItemList):
    return items

```

FastAPI supports these type annotations and will create a Pydantic `TypeAdapter` for them, so that types can work as normally and there's no need for the custom logic and types in RootModels.

## Use one HTTP operation per function

Don't mix HTTP operations in a single function, having one function per HTTP operation helps separate concerns and organize the code.

	peerRESTStorageClass    = "storage-class"
	peerRESTEnableSha256    = "enableSha256"
	peerRESTEnableMultipart = "enableMultipart"
	peerRESTAccessKey       = "access-key"
	peerRESTMetricsTypes    = "types"
	peerRESTDisk            = "disk"
	peerRESTHost            = "host"
	peerRESTJobID           = "job-id"
	peerRESTDepID           = "depID"
	peerRESTStartRebalance  = "start-rebalance"
	peerRESTMetrics         = "metrics"

Mais vous pouvez les réorganiser, et avoir la valeur sans défaut (le paramètre de requête `q`) en premier.

Cela n'a pas d'importance pour **FastAPI**. Il détectera les paramètres par leurs noms, types et déclarations par défaut (`Query`, `Path`, etc), il ne se soucie pas de l'ordre.

Ainsi, vous pouvez déclarer votre fonction comme suit :

{* ../../docs_src/path_params_numeric_validations/tutorial002_py310.py hl[7] *}

 */
package org.apache.maven.api.annotations;

import java.lang.annotation.Documented;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;

/**
 * This annotation tags types that are part of an experimental API.
 * Classes or methods annotated with this annotation may be changed / removed without notice.
 *
 * @since 4.0.0
 */
@Experimental
@Documented
@Retention(RetentionPolicy.CLASS)

#define TENSORFLOW_C_EAGER_ABSTRACT_OPERATION_H_

#include <memory>

#include "absl/types/span.h"
#include "tensorflow/c/eager/abstract_tensor_handle.h"
#include "tensorflow/c/tensor_interface.h"
#include "tensorflow/core/framework/tensor_shape.h"
#include "tensorflow/core/framework/types.pb.h"
#include "tensorflow/core/platform/status.h"

namespace tensorflow {

// Abstract interface to an operation.

But you can re-order them, and have the value without a default (the query parameter `q`) first.

It doesn't matter for **FastAPI**. It will detect the parameters by their names, types and default declarations (`Query`, `Path`, etc), it doesn't care about the order.

So, you can declare your function as:

{* ../../docs_src/path_params_numeric_validations/tutorial002_py310.py hl[7] *}

So, if you run this example and go to [http://127.0.0.1:8000/items/foo](http://127.0.0.1:8000/items/foo), you will see a response of:

```JSON
{"item_id":"foo"}
```

## Path parameters with types { #path-parameters-with-types }

You can declare the type of a path parameter in the function, using standard Python type annotations:

{* ../../docs_src/path_params/tutorial002_py310.py hl[7] *}

Da die Parameter mit TypeScript-Typen beschrieben werden (ähnlich den Python-Typhinweisen), ist die Editorunterstützung ziemlich gut.

    /**
     * Enable or disable thumbnail generation for documents.
     * When enabled, thumbnails are generated for supported file types.
     */
    @Size(max = 10)
    public String thumbnail;

    /**
     * Types of crawling failures to ignore during crawling operations.
     * Specified failure types will not be logged or counted as errors.
     */
    @Size(max = 1000)
    public String ignoreFailureType;

    /**