**GraphQL** résout des cas d'utilisation très spécifiques.

Il présente des **avantages** et des **inconvénients** par rapport aux **API web** classiques.

Assurez-vous d'évaluer si les **bénéfices** pour votre cas d'utilisation compensent les **inconvénients**. 🤓

///

## Bibliothèques GraphQL { #graphql-libraries }

Voici quelques bibliothèques **GraphQL** qui prennent en charge **ASGI**. Vous pouvez les utiliser avec **FastAPI** :

            </includes>
            <!-- allowed non-binary backwards compatible changes -->
            <excludes>
              <!-- START default constructor on Plexus/JSR 330 components -->
              <exclude>org.apache.maven.lifecycle.DefaultLifecycleExecutor#DefaultLifecycleExecutor()</exclude>
              <exclude>org.apache.maven.plugin.DefaultBuildPluginManager#DefaultBuildPluginManager()</exclude>

This means that you can install the latest version of Pydantic v2 and import and use the old Pydantic v1 components from this submodule, as if you had the old Pydantic v1 installed.

{* ../../docs_src/pydantic_v1_in_v2/tutorial001_an_py310.py hl[1,4] *}

### FastAPI support for Pydantic v1 in v2 { #fastapi-support-for-pydantic-v1-in-v2 }

Todo construido como herramientas y componentes reutilizables que son fáciles de integrar con tus sistemas, almacenes de datos, bases de datos relacionales y NoSQL, etc.

### Inyección de dependencias { #dependency-injection }

[macrobenchmarks](https://elasticsearch-benchmarks.elastic.co/app/kibana#/dashboard/Nightly-Benchmark-Overview) with
[Rally](http://github.com/elastic/rally). Microbenchmarks are intended to spot performance regressions in performance-critical components.
The microbenchmark suite is also handy for ad-hoc microbenchmarks but please remove them again before merging your PR.

## Getting Started

Just run `gradlew -p benchmarks run` from the project root

[Analysis] - SuggestAnalyzer
```

Note: Suggester has TWO ReadingConverter instances:
- `readingConverter` - For query/metadata fields
- `contentsReadingConverter` - For content/document fields

---

## Key Components

### Suggester (Main Entry Point)
Location: `src/main/java/org/codelibs/fess/suggest/Suggester.java`

        assertFalse(AdminLogAction.isLogFilename(""));
    }

    @Test
    public void test_isLogFilename_withPathSeparators() {
        // isLogFilename only checks the file extension, not path components
        assertTrue(AdminLogAction.isLogFilename("subdir/fess.log"));
        assertTrue(AdminLogAction.isLogFilename("../fess.log"));
    }

                    return builder.build();
                }
            }
            return query;
        }

        /**
         * Splits a field name into its components.
         *
         * @param defaultField the default field name
         * @param field the field name to split
         * @return a Pair containing the field name and extension key
         */

Mas esse exemplo ainda é valido e mostra como interagir com os componentes internos.

///

Também podemos usar essa mesma abordagem para acessar o corpo da requisição em um manipulador de exceção.

Tudo que precisamos fazer é manipular a requisição dentro de um bloco `try`/`except`:

Tudo construído como ferramentas e componentes reutilizáveis que são fáceis de integrar com seus sistemas, armazenamento de dados, banco de dados relacionais e não-relacionais etc.

### Injeção de dependência { #dependency-injection }