Depois é só fazer o mesmo nos seus testes.

Por exemplo:

* Para passar um parâmetro *path* ou *query*, adicione-o à própria URL.
* Para passar um corpo JSON, passe um objeto Python (por exemplo, um `dict`) para o parâmetro `json`.
* Se você precisar enviar *Dados de Formulário* em vez de JSON, use o parâmetro `data`.

所有这些消息都将使用同一个 WebSocket 连接。

## 使用 `Depends` 和其他依赖项 { #using-depends-and-others }

在 WebSocket 端点中，您可以从 `fastapi` 导入并使用以下内容：

* `Depends`
* `Security`
* `Cookie`
* `Header`
* `Path`
* `Query`

它们的工作方式与其他 FastAPI 端点/*路径操作* 相同：

{* ../../docs_src/websockets_/tutorial002_an_py310.py hl[68:69,82] *}

/// info

由于这是一个 WebSocket，抛出 `HTTPException` 并不是很合理，而是抛出 `WebSocketException`。

### Parâmetros do Pydantic v1 { #pydantic-v1-parameters }

Se você precisar usar algumas das ferramentas específicas do FastAPI para parâmetros como `Body`, `Query`, `Form` etc. com modelos do Pydantic v1, pode importá-las de `fastapi.temp_pydantic_v1_params` enquanto conclui a migração para o Pydantic v2:

{* ../../docs_src/pydantic_v1_in_v2/tutorial004_an_py310.py hl[4,18] *}

labels.num=Número
labels.pn=Número de página
labels.protocolScheme=Esquema
labels.purgeByBots=Eliminar por Bots
labels.logLevel=Nivel de registro
labels.purgeSearchLogDay=Eliminar registros de búsqueda
labels.query=Consulta
labels.queryId=ID de consulta
labels.rt=rt
labels.searchLog=Registro de búsqueda
labels.sort=Ordenar
labels.start=Posición de inicio
labels.loginRequired=Requiere inicio de sesión

labels.lastAccessTime=최종 접근 일시
labels.notificationTo=알림 대상
labels.num=수
labels.pn=페이지 번호
labels.protocolScheme=스키마
labels.purgeByBots=봇 삭제
labels.logLevel=로그 레벨
labels.purgeSearchLogDay=검색 로그 삭제
labels.query=쿼리
labels.queryId=쿼리 ID
labels.rt=rt
labels.searchLog=검색 로그
labels.sort=정렬
labels.start=시작 위치
labels.loginRequired=로그인 필요
labels.loginLink=로그인 링크 표시
labels.threadName=스레드 이름
labels.url=URL
labels.userFavorite=즐겨찾기 로그

{* ../../docs_src/background_tasks/tutorial002_an_py310.py hl[13,15,22,25] *}


In this example, the messages will be written to the `log.txt` file *after* the response is sent.

If there was a query in the request, it will be written to the log in a background task.

And then another background task generated at the *path operation function* will write a message using the `email` path parameter.

import org.codelibs.fess.unit.UnitFessTestCase;
import org.codelibs.fess.util.ComponentUtil;
import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.TestInfo;
import org.opensearch.index.query.QueryBuilder;

public class DataIndexHelperTest extends UnitFessTestCase {

    private DataIndexHelper dataIndexHelper;

    @Override
    protected void setUp(TestInfo testInfo) throws Exception {

    internal fun redactUrl(url: HttpUrl): String {
      if (queryParamsNameToRedact.isEmpty() || url.querySize == 0) {
        return url.toString()
      }
      return url
        .newBuilder()
        .query(null)
        .apply {
          for (i in 0 until url.querySize) {
            val parameterName = url.queryParameterName(i)

  }

  /**
   * {@inheritDoc}
   *
   * <p>This implementation of {@code getAllPresent} lacks any insight into the internal cache data
   * structure, and is thus forced to return the query keys instead of the cached keys. This is only
   * possible with an unsafe cast which requires {@code keys} to actually be of type {@code K}.
   *
   * @since 11.0
   */
  /*

 * Futures.addCallback}.) Still, direct {@code addListener} calls are occasionally useful:
 *
 * {@snippet :
 * final String name = ...;
 * inFlight.add(name);
 * ListenableFuture<Result> future = service.query(name);
 * future.addListener(new Runnable() {
 *   public void run() {
 *     processedCount.incrementAndGet();
 *     inFlight.remove(name);
 *     lastProcessed.set(name);
 *     logger.info("Done with {0}", name);