Search Options

Results per page
Sort
Preferred Languages
Advance

Results 91 - 100 of 1,214 for descriptions (0.06 sec)

  1. tests/test_tutorial/test_request_files/test_tutorial001_03.py

                        },
                        "responses": {
                            "200": {
                                "description": "Successful Response",
                                "content": {"application/json": {"schema": {}}},
                            },
                            "422": {
                                "description": "Validation Error",
                                "content": {
                                    "application/json": {
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Dec 17 20:41:43 UTC 2025
    - 6.2K bytes
    - Viewed (0)
  2. fastapi/security/api_key.py

            self,
            location: APIKeyIn,
            name: str,
            description: Union[str, None],
            scheme_name: Union[str, None],
            auto_error: bool,
        ):
            self.auto_error = auto_error
    
            self.model: APIKey = APIKey(
                **{"in": location},
                name=name,
                description=description,
            )
            self.scheme_name = scheme_name or self.__class__.__name__
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Dec 17 21:25:59 UTC 2025
    - 9.6K bytes
    - Viewed (1)
  3. tests/test_openapi_servers.py

    from fastapi import FastAPI
    from fastapi.testclient import TestClient
    from inline_snapshot import snapshot
    
    app = FastAPI(
        servers=[
            {"url": "/", "description": "Default, relative server"},
            {
                "url": "http://staging.localhost.tiangolo.com:8000",
                "description": "Staging but actually localhost still",
            },
            {"url": "https://prod.example.com"},
        ]
    )
    
    
    @app.get("/foo")
    def foo():
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Sat Dec 27 18:19:10 UTC 2025
    - 1.7K bytes
    - Viewed (0)
  4. tests/test_tutorial/test_schema_extra_example/test_tutorial003.py

                        },
                        "responses": {
                            "200": {
                                "description": "Successful Response",
                                "content": {"application/json": {"schema": {}}},
                            },
                            "422": {
                                "description": "Validation Error",
                                "content": {
                                    "application/json": {
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Fri Dec 26 10:43:02 UTC 2025
    - 5.1K bytes
    - Viewed (0)
  5. docs_src/app_testing/app_b_an_py39/test_main.py

            "/items/",
            headers={"X-Token": "coneofsilence"},
            json={"id": "foobar", "title": "Foo Bar", "description": "The Foo Barters"},
        )
        assert response.status_code == 200
        assert response.json() == {
            "id": "foobar",
            "title": "Foo Bar",
            "description": "The Foo Barters",
        }
    
    
    def test_create_item_bad_token():
        response = client.post(
            "/items/",
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Thu Aug 15 22:31:16 UTC 2024
    - 1.8K bytes
    - Viewed (0)
  6. docs/es/docs/how-to/separate-openapi-schemas.md

    {* ../../docs_src/separate_openapi_schemas/tutorial001_py310.py ln[1:15] hl[14] *}
    
    ...entonces el campo `description` **no será requerido**. Porque tiene un valor por defecto de `None`.
    
    ### Modelo de Entrada en la Documentación { #input-model-in-docs }
    
    Puedes confirmar eso en la documentación, el campo `description` no tiene un **asterisco rojo**, no está marcado como requerido:
    
    <div class="screenshot">
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Tue Dec 16 16:33:45 UTC 2025
    - 4.8K bytes
    - Viewed (0)
  7. docs/pt/docs/how-to/separate-openapi-schemas.md

    {* ../../docs_src/separate_openapi_schemas/tutorial001_py310.py ln[1:15] hl[14] *}
    
    ... então o campo `description` **não será obrigatório**. Porque ele tem um valor padrão de `None`.
    
    ### Modelo de Entrada na Documentação { #input-model-in-docs }
    
    Você pode confirmar que na documentação, o campo `description` não tem um **asterisco vermelho**, não é marcado como obrigatório:
    
    <div class="screenshot">
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Nov 12 16:23:57 UTC 2025
    - 4.8K bytes
    - Viewed (0)
  8. tests/test_tutorial/test_request_files/test_tutorial003.py

                        },
                        "responses": {
                            "200": {
                                "description": "Successful Response",
                                "content": {"application/json": {"schema": {}}},
                            },
                            "422": {
                                "description": "Validation Error",
                                "content": {
                                    "application/json": {
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Dec 17 20:41:43 UTC 2025
    - 7.5K bytes
    - Viewed (0)
  9. internal/config/identity/openid/help.go

    	}
    
    	Help = config.HelpKVS{
    		config.HelpKV{
    			Key:         DisplayName,
    			Description: "Friendly display name for this Provider/App" + defaultHelpPostfix(DisplayName),
    			Optional:    true,
    			Type:        "string",
    		},
    		config.HelpKV{
    			Key:         ConfigURL,
    			Description: `openid discovery document e.g. "https://accounts.google.com/.well-known/openid-configuration"` + defaultHelpPostfix(ConfigURL),
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Fri Jun 23 14:45:27 UTC 2023
    - 4.3K bytes
    - Viewed (0)
  10. impl/maven-cli/src/test/java/org/apache/maven/cling/invoker/mvnup/goals/DomUtilsTest.java

            // Test creating new element
            Element description = DomUtils.updateOrCreateChildElement(root, "description", "Test Description");
            assertNotNull(description, "Should return created element");
    
            xmlOutput = DomUtils.toXml(doc);
            assertTrue(xmlOutput.contains("<description>Test Description</description>"), "Should contain new description");
    
            // Verify element ordering is maintained
    Registered: Sun Dec 28 03:35:09 UTC 2025
    - Last Modified: Tue Nov 18 18:03:26 UTC 2025
    - 31.3K bytes
    - Viewed (0)
Back to top