- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 1,224 for your (0.17 sec)
-
docs/en/docs/tutorial/handling-errors.md
It should be this way because if you have a Pydantic `ValidationError` in your *response* or anywhere in your code (not in the client's *request*), it's actually a bug in your code. And while you fix it, your clients/users shouldn't have access to internal information about the error, as that could expose a security vulnerability. ### Override the `HTTPException` error handler The same way, you can override the `HTTPException` handler.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri Mar 22 01:42:11 GMT 2024 - 9.1K bytes - Viewed (0) -
README.md
subject to change. They can be modified in any way, or even removed, at any time. If your code is a library itself (i.e., it is used on the CLASSPATH of users outside your own control), you should not use beta APIs unless you [repackage] them. **If your code is a library, we strongly recommend using the [Guava Beta Checker] to ensure that you do not use any `@Beta` APIs!**
Plain Text - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Wed May 01 18:44:57 GMT 2024 - 5.9K bytes - Viewed (0) -
docs/en/docs/tutorial/body.md
# Request Body When you need to send data from a client (let's say, a browser) to your API, you send it as a **request body**. A **request** body is data sent by the client to your API. A **response** body is the data your API sends to the client. Your API almost always has to send a **response** body. But clients don't necessarily need to send **request** bodies all the time.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri Mar 22 01:42:11 GMT 2024 - 7.3K bytes - Viewed (0) -
docs/en/docs/advanced/openapi-webhooks.md
You also define in some way at which **moments** your app will send those requests or events. And **your users** define in some way (for example in a web dashboard somewhere) the **URL** where your app should send those requests.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 2.8K bytes - Viewed (0) -
docs/en/docs/advanced/openapi-callbacks.md
# OpenAPI Callbacks You could create an API with a *path operation* that could trigger a request to an *external API* created by someone else (probably the same developer that would be *using* your API).
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 7.7K bytes - Viewed (0) -
docs/en/docs/advanced/path-operation-advanced-configuration.md
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" {!../../../docs_src/path_operation_advanced_configuration/tutorial002.py!} ``` !!! tip
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) -
.github/workflows/codeql-analysis.yml
languages: ${{ matrix.language }} tools: latest # If you wish to specify custom queries, you can do so here or in a config file. # By default, queries listed here will override any specified in a config file. # Prefix the list here with "+" to use these queries and those in the config file. # queries: ./path/to/local/query, your-org/your-repo/queries@main - name: Compile with Gradle with Build Scan
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 09:13:16 GMT 2024 - 4K bytes - Viewed (0) -
docs/en/docs/tutorial/metadata.md
## Docs URLs You can configure the two documentation user interfaces included: * **Swagger UI**: served at `/docs`. * You can set its URL with the parameter `docs_url`. * You can disable it by setting `docs_url=None`. * **ReDoc**: served at `/redoc`. * You can set its URL with the parameter `redoc_url`. * You can disable it by setting `redoc_url=None`.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Sun Mar 31 23:52:53 GMT 2024 - 5.8K bytes - Viewed (0) -
docs/en/docs/tutorial/security/first-steps.md
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Wed Mar 13 19:02:19 GMT 2024 - 8.9K bytes - Viewed (0) -
docs/en/docs/advanced/websockets.md
And to communicate using WebSockets with your backend you would probably use your frontend's utilities. Or you might have a native mobile application that communicates with your WebSocket backend directly, in native code. Or you might have any other way to communicate with the WebSocket endpoint. ---
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 6.2K bytes - Viewed (0)