- Sort Score
- Num 10 results
- Language All
Results 301 - 310 of 445 for item_1 (0.17 seconds)
-
internal/store/store.go
// Target - store target interface type Target interface { Name() string SendFromStore(key Key) error } // Store - Used to persist items. type Store[I any] interface { Put(item I) (Key, error) PutMultiple(item []I) (Key, error) Get(key Key) (I, error) GetMultiple(key Key) ([]I, error) GetRaw(key Key) ([]byte, error) PutRaw(b []byte) (Key, error) Len() int List() []KeyCreated: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Sun Sep 28 20:59:21 GMT 2025 - 4.2K bytes - Click Count (0) -
docs/fr/docs/advanced/behind-a-proxy.md
Par exemple, disons que vous définissez un *chemin d'accès* `/items/` : {* ../../docs_src/behind_a_proxy/tutorial001_01_py310.py hl[6] *} Si le client essaie d'aller à `/items`, par défaut, il sera redirigé vers `/items/`. Mais avant de définir l'option de CLI `--forwarded-allow-ips`, il pourrait rediriger vers `http://localhost:8000/items/`.Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 19 18:37:13 GMT 2026 - 17.4K bytes - Click Count (0) -
docs/pt/docs/advanced/behind-a-proxy.md
Por exemplo, suponha que você defina uma *operação de rota* `/items/`: {* ../../docs_src/behind_a_proxy/tutorial001_01_py310.py hl[6] *} Se o cliente tentar ir para `/items`, por padrão, ele seria redirecionado para `/items/`. Mas antes de definir a opção de linha de comando `--forwarded-allow-ips`, poderia redirecionar para `http://localhost:8000/items/`.Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 19 18:20:43 GMT 2026 - 16.6K bytes - Click Count (0) -
tests/test_forms_single_param.py
}, "HTTPValidationError": { "properties": { "detail": { "items": { "$ref": "#/components/schemas/ValidationError" }, "type": "array", "title": "Detail",Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Sun Feb 08 10:18:38 GMT 2026 - 4.1K bytes - Click Count (0) -
tests/test_reponse_set_reponse_code_empty.py
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Sun Feb 08 10:18:38 GMT 2026 - 3.6K bytes - Click Count (0) -
docs/fr/docs/how-to/migrate-from-pydantic-v1-to-pydantic-v2.md
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 19 18:37:13 GMT 2026 - 6.2K bytes - Click Count (0) -
docs/zh/docs/how-to/migrate-from-pydantic-v1-to-pydantic-v2.md
``` 在某些情况下,甚至可以在 FastAPI 应用的同一个路径操作中同时使用 Pydantic v1 和 v2 模型: {* ../../docs_src/pydantic_v1_in_v2/tutorial003_an_py310.py hl[2:3,6,12,21:22] *} 在上面的示例中,输入模型是 Pydantic v1 模型,输出模型(在 `response_model=ItemV2` 中定义)是 Pydantic v2 模型。 ### Pydantic v1 参数 { #pydantic-v1-parameters } 如果你需要在 Pydantic v1 模型中使用 FastAPI 特有的参数工具,如 `Body`、`Query`、`Form` 等,在完成向 Pydantic v2 的迁移前,可以从 `fastapi.temp_pydantic_v1_params` 导入它们:Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Fri Mar 20 17:06:37 GMT 2026 - 5.1K bytes - Click Count (0) -
tests/test_request_params/test_file/test_list.py
body_model_name = get_body_model_name(openapi, path) assert app.openapi()["components"]["schemas"][body_model_name] == { "properties": { "p": { "type": "array", "items": { "type": "string", "contentMediaType": "application/octet-stream", }, "title": "P", }, }, "required": ["p"],
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Sat Feb 21 13:01:31 GMT 2026 - 11.6K bytes - Click Count (0) -
tests/test_request_params/test_header/test_list.py
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Sun Feb 08 10:18:38 GMT 2026 - 11.3K bytes - Click Count (0) -
guava-testlib/src/com/google/common/testing/RelationshipTester.java
Item<T> itemInfo = getItem(groupNumber, itemNumber); Item<T> relatedInfo = getItem(groupNumber, relatedItemNumber); T item = itemInfo.value; T related = relatedInfo.value; assertWithTemplate( "$ITEM must be $RELATIONSHIP to $OTHER", itemInfo, relatedInfo, equivalence.equivalent(item, related));
Created: Fri Apr 03 12:43:13 GMT 2026 - Last Modified: Sat Aug 09 01:14:59 GMT 2025 - 5.9K bytes - Click Count (0)