- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 263 for yield4 (0.18 sec)
-
subprojects/core/src/test/groovy/org/gradle/api/internal/tasks/options/OptionReaderTest.groovy
Registered: Wed Jun 12 18:38:38 UTC 2024 - Last Modified: Thu Aug 10 12:45:01 UTC 2023 - 33.4K bytes - Viewed (0) -
staging/src/k8s.io/apiextensions-apiserver/pkg/registry/customresourcedefinition/strategy_test.go
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Wed Apr 24 18:25:29 UTC 2024 - 44.6K bytes - Viewed (0) -
docs/en/docs/tutorial/dependencies/dependencies-with-yield.md
# Dependencies with yield FastAPI supports dependencies that do some <abbr title='sometimes also called "exit code", "cleanup code", "teardown code", "closing code", "context manager exit code", etc.'>extra steps after finishing</abbr>. To do this, use `yield` instead of `return`, and write the extra steps (code) after. !!! tip Make sure to use `yield` one single time. !!! note "Technical Details" Any function that is valid to use with:
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Sat Feb 24 23:06:37 UTC 2024 - 14.1K bytes - Viewed (0) -
docs/de/docs/tutorial/dependencies/dependencies-with-yield.md
# Abhängigkeiten mit yield FastAPI unterstützt Abhängigkeiten, die nach Abschluss einige <abbr title="Manchmal auch genannt „Exit Code“, „Cleanup Code“, „Teardown Code“, „Closing Code“, „Kontext Manager Exit Code“, usw.">zusätzliche Schritte ausführen</abbr>. Verwenden Sie dazu `yield` statt `return` und schreiben Sie die zusätzlichen Schritte / den zusätzlichen Code danach. !!! tip "Tipp" Stellen Sie sicher, dass Sie `yield` nur einmal pro Abhängigkeit verwenden.
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Sat Mar 30 18:10:29 UTC 2024 - 13.5K bytes - Viewed (0) -
docs/ru/docs/tutorial/dependencies/dependencies-with-yield.md
**FastAPI** использует их "под капотом" с этой целью. ## Зависимости с `yield` и `HTTPException` Вы видели, что можно использовать зависимости с `yield` совместно с блоком `try`, отлавливающие исключения. Таким же образом вы можете поднять исключение `HTTPException` или что-то подобное в завершающем коде, после `yield`.
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Tue Apr 02 04:21:06 UTC 2024 - 19.6K bytes - Viewed (0) -
docs/zh/docs/tutorial/dependencies/dependencies-with-yield.md
在 `yield` 后抛出 `HTTPException` 或类似的异常是很诱人的,但是**这不起作用**。 带有`yield`的依赖中的退出代码在响应发送之后执行,因此[异常处理程序](../handling-errors.md#install-custom-exception-handlers){.internal-link target=_blank}已经运行过。没有任何东西可以捕获退出代码(在`yield`之后)中的依赖抛出的异常。 所以,如果在`yield`之后抛出`HTTPException`,默认(或任何自定义)异常处理程序捕获`HTTPException`并返回HTTP 400响应的机制将不再能够捕获该异常。 这就是允许在依赖中设置的任何东西(例如数据库会话(DB session))可以被后台任务使用的原因。 后台任务在响应发送之后运行。因此,无法触发`HTTPException`,因为甚至没有办法更改*已发送*的响应。
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Thu Apr 18 19:53:19 UTC 2024 - 10.3K bytes - Viewed (0) -
docs/ja/docs/tutorial/dependencies/dependencies-with-yield.md
**FastAPI** はこれを実現するために内部的に使用しています。 ## `yield`と`HTTPException`を持つ依存関係 `yield`と例外をキャッチする`try`ブロックを持つことができる依存関係を使用することができることがわかりました。 `yield`の後の終了コードで`HTTPException`などを発生させたくなるかもしれません。しかし**それはうまくいきません** `yield`を持つ依存関係の終了コードは[例外ハンドラ](../handling-errors.md#_4){.internal-link target=_blank}の*後に*実行されます。依存関係によって投げられた例外を終了コード(`yield`の後)でキャッチするものはなにもありません。
Registered: Mon Jun 17 08:32:26 UTC 2024 - Last Modified: Thu Apr 18 19:53:19 UTC 2024 - 12.5K bytes - Viewed (0) -
src/encoding/csv/reader_test.go
Name: "FieldCRCR", Input: "§field\r\rfield\r\r", Output: [][]string{{"field\r\rfield\r"}}, }, { Name: "FieldCRCRLF", Input: "§field\r\r\n¶§field\r\r\n", Output: [][]string{{"field\r"}, {"field\r"}}, }, { Name: "FieldCRCRLFCR", Input: "§field\r\r\n¶§\rfield\r\r\n\r", Output: [][]string{{"field\r"}, {"\rfield\r"}}, }, { Name: "FieldCRCRLFCRCR", Input: "§field\r\r\n¶§\r\rfield\r\r\n¶§\r\r",
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Sat May 14 04:25:13 UTC 2022 - 19.1K bytes - Viewed (0) -
staging/src/k8s.io/apiserver/pkg/cel/openapi/values_test.go
lhs: UnstructuredToVal(map[string]interface{}{"field1": "a", "field2": "b"}, objectSchema), rhs: UnstructuredToVal(map[string]interface{}{"field1": "a", "field2": "b"}, objectSchema), equal: true, }, { name: "objects are equal regardless of field order", lhs: UnstructuredToVal(map[string]interface{}{"field1": "a", "field2": "b"}, objectSchema),
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Mon Oct 23 22:30:17 UTC 2023 - 17.7K bytes - Viewed (0) -
staging/src/k8s.io/apiextensions-apiserver/pkg/apiserver/schema/cel/values_test.go
lhs: UnstructuredToVal(map[string]interface{}{"field1": "a", "field2": "b"}, &objectSchema), rhs: UnstructuredToVal(map[string]interface{}{"field1": "a", "field2": "b"}, &objectSchema), equal: true, }, { name: "objects are equal regardless of field order", lhs: UnstructuredToVal(map[string]interface{}{"field1": "a", "field2": "b"}, &objectSchema),
Registered: Sat Jun 15 01:39:40 UTC 2024 - Last Modified: Thu May 16 20:13:14 UTC 2024 - 17.3K bytes - Viewed (0)