Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1181 - 1190 of 1,545 for description (0.58 sec)

  1. docs/de/docs/tutorial/schema-extra-example.md

    Jedes spezifische Beispiel-`dict` in den `examples` kann Folgendes enthalten:
    
    * `summary`: Kurze Beschreibung für das Beispiel.
    * `description`: Eine lange Beschreibung, die Markdown-Text enthalten kann.
    * `value`: Dies ist das tatsächlich angezeigte Beispiel, z. B. ein `dict`.
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Sun Oct 06 20:36:54 UTC 2024
    - 13.2K bytes
    - Viewed (0)
  2. LICENSE

          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.
    
       Copyright [yyyy] [name of copyright owner]
    
    Registered: Thu Oct 31 13:40:30 UTC 2024
    - Last Modified: Tue May 08 21:35:34 UTC 2018
    - 11.1K bytes
    - Viewed (0)
  3. licenses/cloud.google.com/go/compute/metadata/LICENSE

          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.
    
       Copyright [yyyy] [name of copyright owner]
    
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Tue Nov 01 23:31:22 UTC 2022
    - 11.1K bytes
    - Viewed (0)
  4. licenses/github.com/census-instrumentation/opencensus-proto/LICENSE

          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.
    
       Copyright [yyyy] [name of copyright owner]
    
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Sat Oct 26 02:47:39 UTC 2019
    - 11.1K bytes
    - Viewed (0)
  5. licenses/github.com/containernetworking/cni/LICENSE

          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.
    
       Copyright {yyyy} {name of copyright owner}
    
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Tue Jun 16 20:42:16 UTC 2020
    - 11.1K bytes
    - Viewed (0)
  6. licenses/github.com/envoyproxy/protoc-gen-validate/LICENSE

          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.
    
       Copyright [yyyy] [name of copyright owner]
    
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Sat Oct 26 02:47:39 UTC 2019
    - 11.1K bytes
    - Viewed (0)
  7. licenses/github.com/go-openapi/swag/LICENSE

          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.
    
       Copyright [yyyy] [name of copyright owner]
    
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Sat Oct 26 02:47:39 UTC 2019
    - 11.1K bytes
    - Viewed (0)
  8. licenses/github.com/golang/groupcache/LICENSE

    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.
    
       Copyright [yyyy] [name of copyright owner]
    
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Sat Oct 26 02:47:39 UTC 2019
    - 10K bytes
    - Viewed (0)
  9. licenses/github.com/modern-go/concurrent/LICENSE

          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.
    
       Copyright [yyyy] [name of copyright owner]
    
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Sat Oct 26 02:47:39 UTC 2019
    - 11.1K bytes
    - Viewed (0)
  10. licenses/github.com/prometheus/prometheus/LICENSE

          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.
    
       Copyright [yyyy] [name of copyright owner]
    
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Wed Jul 14 16:53:19 UTC 2021
    - 11.1K bytes
    - Viewed (0)
Back to top