ksp = { id = "com.google.devtools.ksp", version.ref = "ksp" }
gradle-lint = { id = "com.android.lint", version.ref = "lint-gradle" }
maven-publish = { id = "com.vanniktech.maven.publish.base", version.ref = "maven-publish" }
maven-sympathy = { id = "io.github.usefulness.maven-sympathy", version.ref = "maven-sympathy" }
mrjar = { id = "me.champeau.mrjar", version.ref = "mrjar" }
shadow = { id = "com.gradleup.shadow", version.ref = "shadow-plugin" }

# This Dockerfile creates an image that has:
# - the correct MTU setting for networking from inside the container to work.
# - Visual Studio 2022 Build Tools
# - MSVC 14.39
# - LLVM/Clang 18.1.4
# - MSYS2 + curl, git, patch, vim, unzip, zip
# - Python 3.9 - 3.14
# - Bazelisk 1.22.1
# - JDK 21 (Azul Zulu)

FROM mcr.microsoft.com/windows/servercore:ltsc2022

SHELL ["powershell.exe", "-ExecutionPolicy", "Bypass", "-Command", \

					<div class="me-3">
						<a class="link d-none d-sm-flex" href="${doc.url_link}" data-uri="${doc.url_link}" data-id="${doc.doc_id}"
							data-order="${s.index}"
						> <img src="${fe:url('/images/blank.png')}" alt="thumbnail"
							data-src="${fe:url('/thumbnail/')}?docId=${f:u(doc.doc_id)}&queryId=${f:u(queryId)}" class="thumbnail"
						>
						</a>
					</div>
					</c:if>

<img src="/img/tutorial/path-operation-configuration/image03.png">

## *path operation*を非推奨にする { #deprecate-a-path-operation }

*path operation*を<dfn title="非推奨、使用しないことを推奨">deprecated</dfn>としてマークする必要があるが、それを削除しない場合は、`deprecated`パラメータを渡します:

{* ../../docs_src/path_operation_configuration/tutorial006_py310.py hl[16] *}

対話的ドキュメントでは非推奨と明記されます:

<img src="/img/tutorial/path-operation-configuration/image04.png">

Se você abrir os documentos criados automaticamente para a API, sua extensão aparecerá no final da *operação de rota* específica.

<img src="/img/tutorial/path-operation-advanced-configuration/image01.png">

E se você olhar o esquema OpenAPI resultante (na rota `/openapi.json` da sua API), você verá que a sua extensão também faz parte da *operação de rota* específica:

```JSON hl_lines="22"
{

Ви побачите вашу документацію з розділом «Callbacks» для вашої операції шляху, який показує, як має виглядати зовнішній API:

errors.design_jsp_file_does_not_exist = Le fichier JSP n'existe pas.
errors.design_file_name_is_not_found = Le nom de fichier n'est pas spécifié.
errors.failed_to_write_design_image_file = Échec du téléversement d'un fichier image.
errors.failed_to_update_jsp_file = Échec de la mise à jour du fichier JSP.
errors.design_file_name_is_invalid = Le nom de fichier n'est pas valide.
errors.design_file_is_unsupported_type = Ce type de fichier n'est pas pris en charge.

d=a(this),e=document.createElement("DIV"),f=c.reCaptchaSiteKey||d.valAttr("recaptcha-sitekey"),g=c.reCaptchaTheme||d.valAttr("recaptcha-theme")||"light",h=c.reCaptchaSize||d.valAttr("recaptcha-size")||"normal",i=c.reCaptchaType||d.valAttr("recaptcha-type")||"image";if(!f)throw new Error("Google reCaptcha site key is required.");var j=grecaptcha.render(e,{sitekey:f,theme:g,size:h,type:i,callback:function(a){b.find('[data-validation~="recaptcha"]').trigger("validation",a&&""!==a)},"expired-callback":function(...

上記の例ではバイト列をストリームしましたが、レスポンスに `Content-Type` ヘッダがないため、クライアントは受け取るデータの種類を認識できませんでした。

`StreamingResponse` を継承したカスタムクラスを作成し、ストリームするデータに応じて `Content-Type` ヘッダを設定できます。

例えば、`media_type` 属性で `Content-Type` を `image/png` に設定する `PNGStreamingResponse` を作成できます:

{* ../../docs_src/stream_data/tutorial002_py310.py ln[6,19:20] hl[20] *}

その後、path operation 関数で `response_class=PNGStreamingResponse` としてこの新しいクラスを使用できます:

```

</div>

## Kontrol Edin { #check-it }

Etkileşimli dokümantasyona gidin: [http://127.0.0.1:8000/docs](http://127.0.0.1:8000/docs).

Şuna benzer bir şey göreceksiniz:

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

/// check | Authorize butonu!

Artık parıl parıl yeni bir "Authorize" butonunuz var.

Ayrıca *path operation*’ınızın sağ üst köşesinde tıklayabileceğiniz küçük bir kilit simgesi de bulunuyor.

///