Search Options

Results per page
Sort
Preferred Languages
Advance

Results 111 - 120 of 225 for sintaxe (0.28 sec)

  1. docs/es/docs/tutorial/path-params-numeric-validations.md

    * declarar el parámetro de query `q` sin un `Query` ni ningún valor por defecto
    * declarar el parámetro de path `item_id` usando `Path`
    * tenerlos en un orden diferente
    * no usar `Annotated`
    
    ...Python tiene una sintaxis especial para eso.
    
    Pasa `*`, como el primer parámetro de la función.
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Mon Dec 30 18:26:57 UTC 2024
    - 6.1K bytes
    - Viewed (0)
  2. pom.xml

    			<version>${junit.jupiter.version}</version>
    			<scope>test</scope>
    		</dependency>
    		<dependency>
    			<groupId>org.junit.vintage</groupId>
    			<artifactId>junit-vintage-engine</artifactId>
    			<version>${junit.vintage.version}</version>
    			<scope>test</scope>
    		</dependency>
    		<dependency>
    			<groupId>org.dbflute.utflute</groupId>
    			<artifactId>utflute-lastaflute</artifactId>
    Registered: Thu Sep 04 12:52:25 UTC 2025
    - Last Modified: Thu Sep 04 05:22:58 UTC 2025
    - 49.6K bytes
    - Viewed (0)
  3. api/maven-api-plugin/src/main/mdo/plugin.mdo

              <name>requiredJavaVersion</name>
              <version>1.1.0+</version>
              <description>
                A version range which specifies the supported Java versions. A version range can either use the usual mathematical syntax "[2.0.10,2.1.0),[3.0,)" or use a single version "2.2.1". The latter is a short form for "[2.2.1,)", i.e. denotes the minimum version required.
                @since Maven 4.0.0-alpha-3
              </description>
    Registered: Sun Sep 07 03:35:12 UTC 2025
    - Last Modified: Tue Feb 25 08:28:41 UTC 2025
    - 24.8K bytes
    - Viewed (0)
  4. docs/en/docs/tutorial/path-params.md

    # Path Parameters { #path-parameters }
    
    You can declare path "parameters" or "variables" with the same syntax used by Python format strings:
    
    {* ../../docs_src/path_params/tutorial001.py hl[6:7] *}
    
    The value of the path parameter `item_id` will be passed to your function as the argument `item_id`.
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Aug 31 10:29:01 UTC 2025
    - 9.3K bytes
    - Viewed (0)
  5. docs/de/docs/deployment/server-workers.md

    [19515] [INFO] Waiting for application startup.
    [19515] [INFO] Application startup complete.
    ```
    
    </div>
    
    Sehen wir uns an, was jede dieser Optionen bedeutet:
    
    * `main:app`: Das ist die gleiche Syntax, die auch von Uvicorn verwendet wird. `main` bedeutet das Python-Modul mit dem Namen `main`, also eine Datei `main.py`. Und `app` ist der Name der Variable, welche die **FastAPI**-Anwendung ist.
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Tue Aug 06 04:48:30 UTC 2024
    - 10.1K bytes
    - Viewed (0)
  6. docs/es/docs/tutorial/first-steps.md

    * el path `/`
    * usando una <abbr title="un método HTTP GET"><code>get</code> operation</abbr>
    
    /// info | Información sobre `@decorator`
    
    Esa sintaxis `@algo` en Python se llama un "decorador".
    
    Lo pones encima de una función. Como un bonito sombrero decorativo (supongo que de ahí viene el término).
    
    Un "decorador" toma la función de abajo y hace algo con ella.
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Mon Dec 30 17:46:44 UTC 2024
    - 12.2K bytes
    - Viewed (0)
  7. LICENSE.txt

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Registered: Fri Sep 05 11:42:10 UTC 2025
    - Last Modified: Mon Jul 23 14:02:28 UTC 2012
    - 11.1K bytes
    - Viewed (0)
  8. LICENSES/vendor/github.com/containerd/ttrpc/LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.2K bytes
    - Viewed (0)
  9. LICENSES/vendor/github.com/coreos/go-systemd/v22/LICENSE

    notice, with the fields enclosed by brackets "[]" replaced with your own
    identifying information. (Don't include the brackets!) The text should be
    enclosed in the appropriate comment syntax for the file format. We also
    recommend that a file or class name and description of purpose be included on
    the same "printed page" as the copyright notice for easier identification within
    third-party archives.
    
    Registered: Fri Sep 05 09:05:11 UTC 2025
    - Last Modified: Wed Jun 16 15:14:16 UTC 2021
    - 10.2K bytes
    - Viewed (0)
  10. LICENSE

          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    Registered: Sun Sep 21 03:50:09 UTC 2025
    - Last Modified: Mon Jan 11 04:26:17 UTC 2021
    - 11.1K bytes
    - Viewed (0)
Back to top