- Sort Score
- Result 10 results
- Languages All
Results 61 - 70 of 226 for redeclare (0.07 sec)
-
docs/pt/docs/tutorial/header-params.md
## importe `Header` Primeiro importe `Header`: {* ../../docs_src/header_params/tutorial001_py310.py hl[1] *} ## Declare parâmetros de `Header` Então declare os paramêtros de cabeçalho usando a mesma estrutura que em `Path`, `Query` e `Cookie`. O primeiro valor é o valor padrão, você pode passar todas as validações adicionais ou parâmetros de anotação:
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Nov 18 02:25:44 UTC 2024 - 3.1K bytes - Viewed (0) -
docs/en/docs/tutorial/extra-models.md
We could do better. We can declare a `UserBase` model that serves as a base for our other models. And then we can make subclasses of that model that inherit its attributes (type declarations, validation, etc). All the data conversion, validation, documentation, etc. will still work as normally.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 7.2K bytes - Viewed (0) -
docs/en/docs/tutorial/path-params.md
/// /// tip If you are wondering, "AlexNet", "ResNet", and "LeNet" are just names of Machine Learning <abbr title="Technically, Deep Learning model architectures">models</abbr>. /// ### Declare a *path parameter* { #declare-a-path-parameter } Then create a *path parameter* with a type annotation using the enum class you created (`ModelName`): {* ../../docs_src/path_params/tutorial005.py hl[16] *}
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 10:29:01 UTC 2025 - 9.3K bytes - Viewed (0) -
src/test/java/jcifs/SmbResourceTest.java
assertEquals(1, existsExceptions.length, "exists() should declare CIFSException"); assertEquals(CIFSException.class, existsExceptions[0], "Should declare CIFSException"); assertEquals(1, getTypeExceptions.length, "getType() should declare CIFSException"); assertEquals(CIFSException.class, getTypeExceptions[0], "Should declare CIFSException"); } @Test
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Thu Aug 14 05:31:44 UTC 2025 - 35K bytes - Viewed (0) -
docs/pt/docs/tutorial/query-param-models.md
/// note | Nota Isso é suportado desde o FastAPI versão `0.115.0`. 🤓 /// ## Parâmetros de Consulta com um Modelo Pydantic Declare os **parâmetros de consulta** que você precisa em um **modelo Pydantic**, e então declare o parâmetro como `Query`: {* ../../docs_src/query_param_models/tutorial001_an_py310.py hl[9:13,17] *}
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Nov 18 02:25:44 UTC 2024 - 2.3K bytes - Viewed (0) -
docs/en/docs/tutorial/schema-extra-example.md
# Declare Request Example Data { #declare-request-example-data } You can declare examples of the data your app can receive. Here are several ways to do it. ## Extra JSON Schema data in Pydantic models { #extra-json-schema-data-in-pydantic-models } You can declare `examples` for a Pydantic model that will be added to the generated JSON Schema. //// tab | Pydantic v2 {* ../../docs_src/schema_extra_example/tutorial001_py310.py hl[13:24] *}
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 9.6K bytes - Viewed (0) -
docs/en/docs/tutorial/response-model.md
/// tip If you have strict type checks in your editor, mypy, etc, you can declare the function return type as `Any`. That way you tell the editor that you are intentionally returning anything. But FastAPI will still do the data documentation, validation, filtering, etc. with the `response_model`. /// ### `response_model` Priority { #response-model-priority }
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 16K bytes - Viewed (0) -
docs/en/docs/advanced/response-headers.md
# Response Headers { #response-headers } ## Use a `Response` parameter { #use-a-response-parameter } You can declare a parameter of type `Response` in your *path operation function* (as you can do for cookies). And then you can set headers in that *temporal* response object. {* ../../docs_src/response_headers/tutorial002.py hl[1, 7:8] *} And then you can return any object you need, as you normally would (a `dict`, a database model, etc).
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 2.3K bytes - Viewed (0) -
docs/en/docs/advanced/response-cookies.md
# Response Cookies { #response-cookies } ## Use a `Response` parameter { #use-a-response-parameter } You can declare a parameter of type `Response` in your *path operation function*. And then you can set cookies in that *temporal* response object. {* ../../docs_src/response_cookies/tutorial002.py hl[1, 8:9] *} And then you can return any object you need, as you normally would (a `dict`, a database model, etc).
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 2.2K bytes - Viewed (0) -
docs/en/docs/tutorial/dependencies/index.md
/// ### Import `Depends` { #import-depends } {* ../../docs_src/dependencies/tutorial001_an_py310.py hl[3] *} ### Declare the dependency, in the "dependant" { #declare-the-dependency-in-the-dependant } The same way you use `Body`, `Query`, etc. with your *path operation function* parameters, use `Depends` with a new parameter:
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 9.6K bytes - Viewed (0)