Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1221 - 1230 of 1,429 for Description (0.09 sec)

  1. LICENSES/vendor/github.com/coredns/corefile-migration/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: Fri Nov 01 09:05:11 UTC 2024
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.2K bytes
    - Viewed (0)
  2. docs/zh/docs/tutorial/first-steps.md

            "title": "FastAPI",
            "version": "0.1.0"
        },
        "paths": {
            "/items/": {
                "get": {
                    "responses": {
                        "200": {
                            "description": "Successful Response",
                            "content": {
                                "application/json": {
    
    
    
    ...
    ```
    
    #### OpenAPI 的用途
    
    驱动 FastAPI 内置的 2 个交互式文档系统的正是 OpenAPI 模式。
    
    Registered: Sun Nov 03 07:19:11 UTC 2024
    - Last Modified: Sun Oct 06 20:36:54 UTC 2024
    - 9.1K bytes
    - Viewed (0)
  3. licenses/cel.dev/expr/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: Mon Apr 08 17:05:56 UTC 2024
    - 11.1K bytes
    - Viewed (0)
  4. licenses/github.com/containernetworking/plugins/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)
  5. licenses/github.com/go-logr/logr/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)
  6. licenses/github.com/google/go-containerregistry/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: Fri Jul 30 04:02:55 UTC 2021
    - 11.1K bytes
    - Viewed (0)
  7. licenses/github.com/google/gofuzz/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/howardjohn/unshare-go/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 2023 John Howard
    
    Registered: Wed Nov 06 22:53:10 UTC 2024
    - Last Modified: Wed Jan 31 07:51:36 UTC 2024
    - 11.1K bytes
    - Viewed (0)
  9. licenses/github.com/moby/buildkit/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: Mon Apr 11 20:58:15 UTC 2022
    - 11.1K bytes
    - Viewed (0)
  10. licenses/github.com/moby/spdystream/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: Thu Apr 22 22:59:25 UTC 2021
    - 11.1K bytes
    - Viewed (0)
Back to top