docs: Refactor and add test for paginated_return_data.py

docs/examples/data_transfer_objects/factory/paginated_return_data.py

@@ -3,14 +3,13 @@
 from sqlalchemy.orm import Mapped
 
 from litestar import Litestar, get
+from litestar.contrib.sqlalchemy.base import UUIDBase
 from litestar.contrib.sqlalchemy.dto import SQLAlchemyDTO
 from litestar.dto import DTOConfig
 from litestar.pagination import ClassicPagination
 
-from .my_lib import Base
 
-
-class User(Base):
+class User(UUIDBase):
     name: Mapped[str]
     password: Mapped[str]
     created_at: Mapped[datetime]

docs/usage/dto/1-abstract-dto.rst

@@ -366,9 +366,14 @@ Working with Litestar's Pagination Types
 Litestar offers paginated response wrapper types, and DTO Factory types can handle this out of the box.
 
 .. literalinclude:: /examples/data_transfer_objects/factory/paginated_return_data.py
-    :caption: Paginated Return Data
     :language: python
-    :linenos:
+    :lines: 9-11,22-39
+
+.. dropdown:: Full Code (click to expand)
+
+    .. literalinclude:: /examples/data_transfer_objects/factory/paginated_return_data.py
+        :language: python
+        :emphasize-lines: 9,22-39
 
 The DTO is defined and configured, in our example, we're excluding ``password`` and ``created_at`` fields from the final
 representation of our users.

tests/examples/test_data_transfer_objects/test_factory/test_paginated_return_data.py

@@ -0,0 +1,17 @@
+from litestar.status_codes import HTTP_200_OK
+from litestar.testing.client import TestClient
+
+
+def test_create_user() -> None:
+    from docs.examples.data_transfer_objects.factory.paginated_return_data import app
+
+    with TestClient(app=app) as client:
+        response = client.get("/users")
+
+    assert response.status_code == HTTP_200_OK
+    assert response.json() == {
+        "current_page": 1,
+        "items": [{"id": 1, "name": "Litestar User"}],
+        "page_size": 10,
+        "total_pages": 1,
+    }