intend to continue publishing the old `okhttp3.mockwebserver` artifact so there’s no urgency to
migrate.)

| Coordinate                                       | Package Name          | Description                       |
|:-------------------------------------------------| :-------------------- | :-------------------------------- |

## Ajouter un résumé et une description { #summary-and-description }

Vous pouvez ajouter un `summary` et une `description` :

{* ../../docs_src/path_operation_configuration/tutorial003_py310.py hl[17:18] *}

## Utiliser la description depuis la docstring { #description-from-docstring }

    assert response.json() == {
        "name": "Baz",
        "description": None,
        "price": 50.2,
        "tax": 10.5,
        "tags": [],
    }


def test_patch_all(client: TestClient):
    response = client.patch(
        "/items/foo",
        json={
            "name": "Fooz",
            "description": "Item description",
            "price": 3,
            "tax": 10.5,

        "title": "FastAPI",
        "version": "0.1.0"
    },
    "paths": {
        "/items/": {
            "get": {
                "responses": {
                    "200": {
                        "description": "Successful Response",
                        "content": {
                            "application/json": {



...
```

#### OpenAPIの目的 { #what-is-openapi-for }

         */
        public DfsInfo3() {
            // Default constructor
        }

        /**
         * DFS path
         */
        public String path;
        /**
         * Comment or description
         */
        public String comment;
        /**
         * DFS state flags
         */
        public int state;
        /**
         * Number of storage servers
         */

    response = client.post(
        "/items/",
        json={"name": "Foo", "price": price, "description": "Some Foo", "tax": 0.3},
    )
    assert response.status_code == 200
    assert response.json() == {
        "name": "Foo",
        "price": 50.5,
        "description": "Some Foo",
        "tax": 0.3,
        "price_with_tax": 50.8,
    }

  `comp:` etc.  At this stage we check if the PR is valid and meets certain
  quality requirements. For example, we check if the CLA is signed, PR has
  sufficient description, if applicable unit tests are added, if it is a
  reasonable contribution (meaning it is not a single liner cosmetic PR).

**2. Valid?**

-   If the PR passes all the quality checks then we go ahead and assign a

                                "description": "Successful Response",
                                "content": {"application/json": {"schema": {}}},
                            },
                            "404": {"description": "Not found"},
                            "403": {"description": "Operation forbidden"},
                            "422": {
                                "description": "Validation Error",

        "title": "FastAPI",
        "version": "0.1.0"
    },
    "paths": {
        "/items/": {
            "get": {
                "responses": {
                    "200": {
                        "description": "Successful Response",
                        "content": {
                            "application/json": {



...
```

#### OpenAPI 的用途 { #what-is-openapi-for }

Perhaps, you forgot to add an `@Incubating` annotation or `@since` in the javadoc.

2. Accept the changes.\
If you are sure that the changes are intentional, follow the steps described in the report.
This includes adding the description of the changes to the `accepted-public-api-changes.json` file, and providing a reason for each change.
You can add the changes to any place in the file, e.g. at the top.

3. Make sure the file with accepted changes is sorted.\