간단한 페이지가 나타날 것입니다:

<img src="/img/tutorial/websockets/image01.png">

입력창에 메시지를 입력하고 전송할 수 있습니다:

<img src="/img/tutorial/websockets/image02.png">

**FastAPI** WebSocket 응용 프로그램이 응답을 돌려줄 것입니다:

<img src="/img/tutorial/websockets/image03.png">

여러 메시지를 전송(그리고 수신)할 수 있습니다:

<img src="/img/tutorial/websockets/image04.png">

모든 메시지는 동일한 WebSocket 연결을 사용합니다.

## `Depends` 및 기타 사용하기

The JSON Schemas of your models will be part of your OpenAPI generated schema, and will be shown in the interactive API docs:

<img src="/img/tutorial/body/image01.png">

And will also be used in the API docs inside each *path operation* that needs them:

<img src="/img/tutorial/body/image02.png">

## Editor support { #editor-support }

```

</div>

그런 다음 `/docs` UI로 이동하면, **FastAPI**가 해당 **model들**을 사용하여 API **문서를 생성**하는 것으르 확인할 수 있습니다. 또한 이 모델들은 데이터를 직렬화하고 검증하는 데에도 사용됩니다.

<div class="screenshot">
<img src="/img/tutorial/sql-databases/image01.png">
</div>

## 여러 모델로 애플리케이션 업데이트

이제 애플리케이션을 약간 **리팩토링**하여 **보안**과 **유연성**을 개선해 보겠습니다.

이전 애플리케이션의 UI를 보면, 지금까지는 클라이언트가 생성할 `Hero`의 `id`를 직접 지정할 수 있다는 것을 알 수 있습니다. 😱

errors.design_jsp_file_does_not_exist = The JSP file does not exist.
errors.design_file_name_is_not_found = The file name is not specified.
errors.failed_to_write_design_image_file = Failed to upload an image file.
errors.failed_to_update_jsp_file = Failed to update the JSP file.
errors.design_file_name_is_invalid = The file name is invalid.
errors.design_file_is_unsupported_type = This file type is unsupported.

errors.design_jsp_file_does_not_exist = The JSP file does not exist.
errors.design_file_name_is_not_found = The file name is not specified.
errors.failed_to_write_design_image_file = Failed to upload an image file.
errors.failed_to_update_jsp_file = Failed to update the JSP file.
errors.design_file_name_is_invalid = The file name is invalid.
errors.design_file_is_unsupported_type = This file type is unsupported.

<img src="/img/tutorial/dependencies/image02.png">

## Сокращение { #shortcut }

Но вы видите, что здесь мы имеем некоторое повторение кода, дважды написав `CommonQueryParams`:

//// tab | Python 3.9+

```Python

//         - key: name
//           value: pick* # match objects with tag 'name', all values starting with 'pick'
//       metadata:
//         - key: content-type
//           value: image/* # match objects with 'content-type', all values starting with 'image/'
//       size:
//         lessThan: "10MiB" # match objects with size less than this value (e.g. 10MiB)
//         greaterThan: 1MiB # match objects with size greater than this value (e.g. 1MiB)

<aside class="main-sidebar sidebar-dark-primary">
	<la:link href="/admin/" styleClass="brand-link text-center">
		<span class="brand-text">
		<c:if test="${empty param.brandName or empty param.logoPath}"><img src="${fe:url('/images/logo-head.png')}" alt="<la:message key="labels.header_brand_name" />" /></c:if
		><c:if test="${not empty param.brandName and not empty param.logoPath}"><img src="${fe:url(param.logoPath)}" alt="${f:h(param.brandName)}" /></c:if>
		</span>

In the next chapter about [FastAPI in Containers - Docker](docker.md){.internal-link target=_blank} I'll explain some strategies you could use to handle the other **deployment concepts**.

I'll show you how to **build your own image from scratch** to run a single Uvicorn process. It is a simple process and is probably what you would want to do when using a distributed container management system like **Kubernetes**.

## Recap { #recap }

Pero declarar el tipo es recomendable, ya que de esa manera tu editor sabrá lo que se pasará como el parámetro `commons`, y entonces podrá ayudarte con el autocompletado, chequeo de tipos, etc:

<img src="/img/tutorial/dependencies/image02.png">

## Atajo { #shortcut }

Pero ves que estamos teniendo algo de repetición de código aquí, escribiendo `CommonQueryParams` dos veces:

//// tab | Python 3.9+

```Python