}

    public void setPath_Terms(ConditionOptionCall<TermsAggregationBuilder> opLambda) {
        setPath_Terms("path", opLambda, null);
    }

    public void setPath_Terms(ConditionOptionCall<TermsAggregationBuilder> opLambda, OperatorCall<BsThumbnailQueueCA> aggsLambda) {
        setPath_Terms("path", opLambda, aggsLambda);
    }

# ボディ - 複数のパラメータ { #body-multiple-parameters }

これまで`Path`と`Query`をどう使うかを見てきましたが、リクエストボディ宣言のより高度な使い方を見てみましょう。

## `Path`、`Query`とボディパラメータを混ぜる { #mix-path-query-and-body-parameters }

まず、もちろん、`Path`と`Query`とリクエストボディのパラメータ宣言は自由に混ぜることができ、 **FastAPI** は何をするべきかを知っています。

また、デフォルトを`None`に設定することで、ボディパラメータをオプションとして宣言することもできます:

{* ../../docs_src/body_multiple_params/tutorial001_an_py310.py hl[18:20] *}

/// note | 備考

///

### Use your tags { #use-your-tags }

Use the `tags` parameter with your *path operations* (and `APIRouter`s) to assign them to different tags:

{* ../../docs_src/metadata/tutorial004_py310.py hl[21,26] *}

/// info

Read more about tags in [Path Operation Configuration](path-operation-configuration.md#tags).

///

### Check the docs { #check-the-docs }

     * @param config the SMB configuration
     * @param filename the path to query information for
     * @param informationLevel the information level to query
     */
    public Trans2QueryPathInformation(final Configuration config, final String filename, final int informationLevel) {
        super(config, SMB_COM_TRANSACTION2, TRANS2_QUERY_PATH_INFORMATION);
        this.path = filename;
        this.informationLevel = informationLevel;

## 機能 { #features }

- **Path Operation エクスプローラー** - アプリケーション内のすべての <dfn title="ルート、エンドポイント">*path operations*</dfn> をサイドバーのツリービューで表示します。クリックして任意のルートまたはルーター定義へジャンプできます。
- **ルート検索** - <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>E</kbd>（macOS: <kbd>Cmd</kbd> + <kbd>Shift</kbd> + <kbd>E</kbd>）で、パス・メソッド・名前で検索できます。
- **CodeLens ナビゲーション** - テストクライアント呼び出し（例: `client.get('/items')`）の上に表示されるクリック可能なリンクから、対応する *path operation* にジャンプし、テストと実装の行き来をすばやく行えます。

/**
 * Form class for handling tag operations in storage management.
 * This form represents tag data including path, name, and associated metadata.
 */
public class TagForm {

    /**
     * The file or directory path associated with this tag.
     */
    @Required
    public String path;

    /**
     * The name of the tag with a maximum length of 100 characters.
     */
    @Required
    @Size(max = 100)

func TestUNCPaths(t *testing.T) {
	testCases := []struct {
		objName string
		pass    bool
	}{
		{"/abcdef", true},
		{"/a/b/c/d/e/f/g", true},
		{string(bytes.Repeat([]byte("界"), 85)), true},
		// Each path component must be <= 255 bytes long.
		{string(bytes.Repeat([]byte("界"), 280)), false},
		{`/p/q/r/s/t`, true},
	}
	dir := t.TempDir()

	// Instantiate posix object to manage a disk
	fs, err := newLocalXLStorage(dir)

*Path operation function* içinde `response_class=StreamingResponse` belirtirseniz, her veri parçasını sırayla göndermek için `yield` kullanabilirsiniz.

{* ../../docs_src/stream_data/tutorial001_py310.py ln[1:23] hl[20,23] *}

FastAPI her veri parçasını olduğu gibi `StreamingResponse`'a verir; JSON'a ya da benzeri bir formata dönüştürmeye çalışmaz.

     * @return a {@code Source} pointing to the located pom or an empty {@code Optional} if none was found by this parser
     */
    @Nonnull
    Optional<Source> locate(@Nonnull Path dir);

    /**
     * Parse the model obtained previously by a previous call to {@link #locate(Path)}.
     *
     * @param source the source to parse, never {@code null}
     * @param options possible parsing options, may be {@code null}

Coroutine’ler, thread’ler, blocking vb. hakkında teknik bilginiz varsa ve FastAPI’nin `async def` ile normal `def` arasındaki farkı nasıl ele aldığını merak ediyorsanız, devam edin.

///

### Path Operasyon Fonksiyonları { #path-operation-functions }

Bir *path operasyon fonksiyonunu* `async def` yerine normal `def` ile tanımladığınızda, (sunucuyu bloklayacağından) doğrudan çağrılmak yerine, harici bir thread pool’da çalıştırılır ve ardından beklenir.