/**
     * File has been modified
     */
    int FILE_ACTION_MODIFIED = 0x00000003;

    /**
     * File has been renamed (old name)
     */
    int FILE_ACTION_RENAMED_OLD_NAME = 0x00000004;

    /**
     * File has been renamed (new name)
     */
    int FILE_ACTION_RENAMED_NEW_NAME = 0x00000005;

    /**
     * File stream has been added
     */

Like `item.model_dump(exclude_unset=True)`.

/// info

In Pydantic v1 the method was called `.dict()`, it was deprecated (but still supported) in Pydantic v2, and renamed to `.model_dump()`.

The examples here use `.dict()` for compatibility with Pydantic v1, but you should use `.model_dump()` instead if you can use Pydantic v2.

///

{* ../../docs_src/generate_clients/tutorial004.py *}

//// tab | Node.js

```Javascript
{!> ../../docs_src/generate_clients/tutorial004.js!}
```

////

With that, the operation IDs would be renamed from things like `items-get_items` to just `get_items`, that way the client generator can generate simpler method names.

{* ../../docs_src/body/tutorial002_py310.py *}

/// info

In Pydantic v1 the method was called `.dict()`, it was deprecated (but still supported) in Pydantic v2, and renamed to `.model_dump()`.

The examples here use `.dict()` for compatibility with Pydantic v1, but you should use `.model_dump()` instead if you can use Pydantic v2.

///

{* ../../docs_src/extra_models/tutorial001_py310.py hl[7,9,14,20,22,27:28,31:33,38:39] *}


/// info

In Pydantic v1 the method was called `.dict()`, it was deprecated (but still supported) in Pydantic v2, and renamed to `.model_dump()`.

The examples here use `.dict()` for compatibility with Pydantic v1, but you should use `.model_dump()` instead if you can use Pydantic v2.

///

### About `**user_in.dict()` { #about-user-in-dict }

         * File was removed from the directory
         */
        FILE_REMOVED,
        /**
         * File was modified in the directory
         */
        FILE_MODIFIED,
        /**
         * Directory was renamed
         */
        DIRECTORY_RENAMED,
        /**
         * File or directory attributes were changed
         */
        ATTRIBUTES_CHANGED
    }

    /**
     * SMB2 File Action constants
     */

    void testGetAction() throws SMBProtocolDecodingException {
        int expectedAction = FileNotifyInformation.FILE_ACTION_RENAMED_NEW_NAME;
        byte[] buffer = createValidNotificationBuffer("renamed.txt", expectedAction);

        notifyInfo.decode(buffer, 0, buffer.length);

        assertEquals(expectedAction, notifyInfo.getAction());
    }

    @Test

        void testRenameToSameFile() throws MalformedURLException, SmbException {
            // Arrange
            doThrow(new SmbException("Cannot rename to same file")).when(smbFile).renameTo(smbFile);

            // Act & Assert
            assertThrows(SmbException.class, () -> smbFile.renameTo(smbFile));
        }

        @Test
        void testCreateNewFileWhenExists() throws SmbException, IOException {
            // Arrange

```JSON
{
    "name": "Foo",
    "price": 50.2
}
```

/// info

In Pydantic v1 the method was called `.dict()`, it was deprecated (but still supported) in Pydantic v2, and renamed to `.model_dump()`.

The examples here use `.dict()` for compatibility with Pydantic v1, but you should use `.model_dump()` instead if you can use Pydantic v2.

///

/// info

In this example, to be able to have both `HTTPException`s in the same code, Starlette's exceptions is renamed to `StarletteHTTPException`:

```Python
from starlette.exceptions import HTTPException as StarletteHTTPException
```

### Reuse **FastAPI**'s exception handlers { #reuse-fastapis-exception-handlers }