}

    /**
     * Returns artifacts exported by Maven core and core extensions. Artifacts are identified by their
     * groupId:artifactId string key.
     */
    public Set<String> getExportedArtifacts() {
        return artifacts;
    }

    /**
     * Returns packages exported by Maven core and core extensions.
     */
    public Map<String, ClassLoader> getExportedPackages() {

    public ClassRealm getClassRealm() {
        return realm;
    }

    /**
     * Returns artifacts exported by the extension, identified by groupId:artifactId string key.
     */
    public Set<String> getExportedArtifacts() {
        return artifacts;
    }

    /**
     * Returns classpath elements exported by the extension.
     */
    public Set<String> getExportedPackages() {
        return packages;
    }

			if reflect.ValueOf(expect).Kind() == reflect.Struct {
				if reflect.ValueOf(got).NumField() == reflect.ValueOf(expect).NumField() {
					exported := false
					for i := 0; i < reflect.ValueOf(got).NumField(); i++ {
						if fieldStruct := reflect.ValueOf(got).Type().Field(i); ast.IsExported(fieldStruct.Name) {
							exported = true
							field := reflect.ValueOf(got).Field(i)
							t.Run(fieldStruct.Name, func(t *testing.T) {

 * the fact that the problem reporter has/should not have information about the calling context and hence cannot provide
 * an expressive source hint for the model problem. Instead, the source hint is configured by the model builder before
 * it delegates to other components that potentially encounter problems. Then, the problem reporter can focus on

# Paramètres de cookie { #cookie-parameters }

Vous pouvez définir des paramètres de cookie de la même manière que vous définissez les paramètres `Query` et `Path`.

## Importer `Cookie` { #import-cookie }

Commencez par importer `Cookie` :

{* ../../docs_src/cookie_params/tutorial001_an_py310.py hl[3] *}

## Déclarer des paramètres `Cookie` { #declare-cookie-parameters }

        assertEquals("Exported 0 documents.", result);
    }

    @Test
    public void test_execute_queryAndFormatChaining() {
        setupMockComponents(Collections.emptyList());

        final String result = indexExportJob.query(QueryBuilders.matchAllQuery()).format("json").execute();

        assertEquals("Exported 0 documents.", result);
    }

public interface ArtifactFilterManager {
    /**
     * Returns a filter for core + extension artifacts.
     *
     * @return the artifact filter
     * @deprecated use {@code META-INF/maven/extension.xml} to define artifacts exported by Maven core and plugin
     *             extensions.
     */
    @Deprecated
    ArtifactFilter getArtifactFilter();

    /**
     * Returns a filter for only the core artifacts.
     *

 * the fact that the problem reporter has/should not have information about the calling context and hence cannot provide
 * an expressive source hint for the model problem. Instead, the source hint is configured by the model builder before
 * it delegates to other components that potentially encounter problems. Then, the problem reporter can focus on

# Paramètres d'en-tête { #header-parameters }

Vous pouvez définir des paramètres `Header` de la même manière que vous définissez des paramètres `Query`, `Path` et `Cookie`.

## Importer `Header` { #import-header }

Commencez par importer `Header` :

{* ../../docs_src/header_params/tutorial001_an_py310.py hl[3] *}

## Déclarer des paramètres `Header` { #declare-header-parameters }

* et en importer le sous-module `items` (le fichier `app/routers/items.py`) et `users` (le fichier `app/routers/users.py`)...

Le module `items` aura une variable `router` (`items.router`). C'est celle que nous avons créée dans le fichier `app/routers/items.py`, c'est un objet `APIRouter`.

Nous faisons ensuite la même chose pour le module `users`.

Nous pourrions aussi les importer ainsi :

```Python