この場合、その *外部 API* がどのようである「べき」かをドキュメント化したくなるでしょう。どんな *path operation* を持ち、どんなボディを受け取り、どんなレスポンスを返すか、などです。

## コールバックのあるアプリ { #an-app-with-callbacks }

例で見ていきます。

あなたが請求書を作成できるアプリを開発していると想像してください。

これらの請求書は `id`、`title`（任意）、`customer`、`total` を持ちます。

あなたの API の利用者（外部開発者）は、POST リクエストであなたの API に請求書を作成します。

その後、あなたの API は（仮にこうしましょう）:

* 外部開発者の顧客に請求書を送ります。
* 代金を回収します。
* API 利用者（外部開発者）に通知を送り返します。

Before FastAPI 0.106.0, raising exceptions after `yield` was not possible, the exit code in dependencies with `yield` was executed *after* the response was sent, so [Exception Handlers](../tutorial/handling-errors.md#install-custom-exception-handlers) would have already run.

// along with this program.  If not, see <http://www.gnu.org/licenses/>.

package sql

import (
	"strings"

	"github.com/alecthomas/participle"
	"github.com/alecthomas/participle/lexer"
)

// Types with custom Capture interface for parsing

// Boolean is a type for a parsed Boolean literal
type Boolean bool

// Capture interface used by participle
func (b *Boolean) Capture(values []string) error {

    * New docs section: [Custom Request and APIRoute class](https://fastapi.tiangolo.com/advanced/custom-request-and-route/).
    * PR [#589](https://github.com/tiangolo/fastapi/pull/589) by [@dmontagu](https://github.com/dmontagu).

        if (robotsTxtHelper != null) {
            robotsTxtHelper.setEnabled(robotsTxtEnabled);
        }

        // httpclient
        final RequestConfig.Builder requestConfigBuilder = RequestConfig.custom();
        final HttpClientBuilder httpClientBuilder = HttpClientBuilder.create();

        final Integer connectionTimeoutParam = getInitParameter(CONNECTION_TIMEOUT_PROPERTY, connectionTimeout, Integer.class);

        // When
        request.setTid(tid);

        // Then
        verify(request, times(1)).setTid(tid);
    }

    @Test
    @DisplayName("Test getOverrideTimeout returns custom timeout")
    void testGetOverrideTimeoutReturnsCustomValue() {
        // Given
        Integer expectedTimeout = 5000;
        when(request.getOverrideTimeout()).thenReturn(expectedTimeout);

        // When

### 바이트 스트리밍 { #stream-bytes }

주요 사용 사례 중 하나는 문자열 대신 `bytes`를 스트리밍하는 것입니다. 물론 그렇게 할 수 있습니다.

{* ../../docs_src/stream_data/tutorial001_py310.py ln[44:47] hl[47] *}

## 사용자 정의 `PNGStreamingResponse` { #a-custom-pngstreamingresponse }

위 예시에서는 바이트 데이터를 스트리밍했지만, 응답에 `Content-Type` 헤더가 없어 클라이언트는 어떤 유형의 데이터를 받는지 알 수 없습니다.

스트리밍하는 데이터 유형에 맞춰 `Content-Type` 헤더를 설정하는 `StreamingResponse`의 하위 클래스를 직접 만들 수 있습니다.

	info := checksumInfoJSON{
		Name:      fmt.Sprintf("part.%d", c.PartNumber),
		Algorithm: c.Algorithm.String(),
		Hash:      hex.EncodeToString(c.Hash),
	}
	return json.Marshal(info)
}

// UnmarshalJSON - custom checksum info unmarshaller
func (c *ChecksumInfo) UnmarshalJSON(data []byte) error {
	var info checksumInfoJSON
	json := jsoniter.ConfigCompatibleWithStandardLibrary
	if err := json.Unmarshal(data, &info); err != nil {

# Side Public License, v 1.

# For third-party dependencies, please put signatures in third-party.txt instead of here.

@defaultMessage spawns threads with vague names; use a custom thread factory and name threads so that you can tell (by its name) which executor it is associated with

java.util.concurrent.Executors#newFixedThreadPool(int)
java.util.concurrent.Executors#newSingleThreadExecutor()

    /**
     * Create path validator with default settings
     */
    public PathValidator() {
        this(260, 255, true, false);
    }

    /**
     * Create path validator with custom settings
     *
     * @param maxPathLength maximum total path length
     * @param maxComponentLength maximum length for path components
     * @param allowUncPaths whether to allow UNC paths