- Sort Score
- Result 10 results
- Languages All
Results 21 - 30 of 51 for names (0.27 sec)
-
docs/en/docs/tutorial/security/simple-oauth2.md
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 12.5K bytes - Viewed (0) -
docs/en/docs/features.md
def main(user_id: str): return user_id # A Pydantic model class User(BaseModel): id: int name: str joined: date ``` That can then be used like: ```Python my_user: User = User(id=3, name="John Doe", joined="2018-07-19") second_user_data = { "id": 4, "name": "Mary", "joined": "2018-11-30", } my_second_user: User = User(**second_user_data) ``` !!! info
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 9.3K bytes - Viewed (0) -
docs/de/docs/tutorial/path-params-numeric-validations.md
Aber Sie können die Reihenfolge der Parameter ändern, den Query-Parameter ohne Defaultwert zuerst. Für **FastAPI** ist es nicht wichtig. Es erkennt die Parameter anhand ihres Namens, ihrer Typen, und ihrer Defaultwerte (`Query`, `Path`, usw.). Es kümmert sich nicht um die Reihenfolge. Sie können Ihre Funktion also so deklarieren: === "Python 3.8 nicht annotiert" !!! tip "Tipp"
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Mar 30 17:59:29 GMT 2024 - 10.2K bytes - Viewed (0) -
docs/de/docs/advanced/events.md
In der technischen ASGI-Spezifikation ist dies Teil des <a href="https://asgi.readthedocs.io/en/latest/specs/lifespan.html" class="external-link" target="_blank">Lifespan Protokolls</a> und definiert Events namens `startup` und `shutdown`. !!! info
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Mar 30 20:30:59 GMT 2024 - 9.1K bytes - Viewed (0) -
docs/de/docs/tutorial/path-params.md
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Mar 30 20:28:59 GMT 2024 - 10.3K bytes - Viewed (0) -
docs/de/docs/tutorial/query-params-str-validations.md
### Pydantic v1 `regex` statt `pattern` Vor Pydantic Version 2 und vor FastAPI Version 0.100.0, war der Name des Parameters `regex` statt `pattern`, aber das ist jetzt <abbr title="deprecated – obsolet, veraltet: Es soll nicht mehr verwendet werden">deprecated</abbr>. Sie könnten immer noch Code sehen, der den alten Namen verwendet: === "Python 3.10+ Pydantic v1" ```Python hl_lines="11"
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Mar 30 17:58:59 GMT 2024 - 27.7K bytes - Viewed (0) -
docs/de/docs/tutorial/response-model.md
=== "Python 3.8+" ```Python hl_lines="31 37" {!> ../../../docs_src/response_model/tutorial005.py!} ``` !!! tip "Tipp" Die Syntax `{"name", "description"}` erzeugt ein `set` mit diesen zwei Werten. Äquivalent zu `set(["name", "description"])`. #### `list`en statt `set`s verwenden
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sat Mar 30 20:26:58 GMT 2024 - 19.9K bytes - Viewed (0) -
docs/en/docs/tutorial/bigger-applications.md
### Avoid name collisions We are importing the submodule `items` directly, instead of importing just its variable `router`. This is because we also have another variable named `router` in the submodule `users`. If we had imported one after the other, like: ```Python from .routers.items import router
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 18.6K bytes - Viewed (0) -
docs/en/docs/tutorial/header-params.md
Most of the standard headers are separated by a "hyphen" character, also known as the "minus symbol" (`-`). But a variable like `user-agent` is invalid in Python. So, by default, `Header` will convert the parameter names characters from underscore (`_`) to hyphen (`-`) to extract and document the headers. Also, HTTP headers are case-insensitive, so, you can declare them with standard Python style (also known as "snake_case").
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Tue Oct 17 05:59:11 GMT 2023 - 5.8K bytes - Viewed (0) -
docs/en/docs/advanced/path-operation-advanced-configuration.md
{!../../../docs_src/path_operation_advanced_configuration/tutorial001.py!} ``` ### Using the *path operation function* name as the operationId If you want to use your APIs' function names as `operationId`s, you can iterate over all of them and override each *path operation's* `operation_id` using their `APIRoute.name`. You should do it after adding all your *path operations*. ```Python hl_lines="2 12-21 24"
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 7.7K bytes - Viewed (0)