tempest-fastapi-sdk 0.78.0__tar.gz → 0.79.0__tar.gz

{tempest_fastapi_sdk-0.78.0 → tempest_fastapi_sdk-0.79.0}/CHANGELOG.md

@@ -5,6 +5,20 @@ All notable changes to **tempest-fastapi-sdk** are listed below.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.79.0] — 2026-06-27
+
+### Changed
+
+- **`BaseService` / `BaseController` `update` payload is now generically
+  typed.** Both classes gained an optional third type parameter
+  `UpdateT` (bound to `BaseSchema`, default `BaseSchema`) so `update`
+  accepts the project's own update schema instead of the bare
+  `BaseSchema`: `BaseService[Repo, Resp, MyUpdateSchema]` /
+  `BaseController[Service, Resp, MyUpdateSchema]`. The default keeps every
+  existing two-argument subclass working unchanged. Implemented with a
+  PEP 695/696 `TypeVar` default via `typing_extensions` (already present
+  through Pydantic).
+
 ## [0.78.0] — 2026-06-27
 
 ### Added

{tempest_fastapi_sdk-0.78.0 → tempest_fastapi_sdk-0.79.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: tempest-fastapi-sdk
-Version: 0.78.0
+Version: 0.79.0
 Summary: Shared FastAPI building blocks: base schemas, ORM model, async repository, exceptions, pagination and settings — the conventions used across Tempest projects.
 Project-URL: Homepage, https://github.com/mauriciobenjamin700/tempest-fastapi-sdk
 Project-URL: Repository, https://github.com/mauriciobenjamin700/tempest-fastapi-sdk
@@ -2126,7 +2126,7 @@ Each mixin owns its own env-var prefix — pick only the ones the service needs:
 
 `BaseService[RepositoryT, ResponseT]` and `BaseController[ServiceT, ResponseT]` are generic skeletons matching the SDK layering (router → controller → service → repository). They expose pass-through CRUD methods so simple endpoints can subclass them without overriding anything; you override only methods that need orchestration.
 
-What you inherit by subclassing `BaseService[RepositoryT, ResponseT]`:
+`BaseService[RepositoryT, ResponseT]` accepts an optional third type argument — `BaseService[RepositoryT, ResponseT, UpdateT]` — that types the `update` payload (defaults to `BaseSchema`, so the two-argument form keeps working). What you inherit by subclassing it:
 
 | Method | Returns | Notes |
 | --- | --- | --- |
@@ -2136,7 +2136,7 @@ What you inherit by subclassing `BaseService[RepositoryT, ResponseT]`:
 | `paginate(filters=None, order_by=None, page=1, page_size=20, ascending=True)` | `dict` with mapped `items` + `total`/`page`/`size`/`pages`. | Offset pagination via `repository.paginate`. |
 | `count(filters=None)` | `int` | Pass-through to `repository.count`. |
 | `exists(filters)` | `bool` | Pass-through to `repository.exists`. |
-| `update(id, data)` | `ResponseT` | Fetch by id, copy the fields present in `data` (a `BaseSchema`) onto the row, persist, map. `to_dict()` drops unset/`None`, so it serves PUT and PATCH alike. |
+| `update(id, data)` | `ResponseT` | Fetch by id, copy the fields present in `data` (typed `UpdateT`, the optional 3rd generic param — defaults to `BaseSchema`) onto the row, persist, map. `to_dict()` drops unset/`None`, so it serves PUT and PATCH alike. |
 | `delete(id)` | `None` | Hard delete via `repository.delete`. |
 
 `map_to_response` is `await`-ed when it returns a coroutine, so async mappers work transparently — no method override needed.
@@ -2149,7 +2149,7 @@ What you inherit by subclassing `BaseController[ServiceT, ResponseT]`:
 | `list(filters, order_by, ascending)` | `service.list` | Same. |
 | `paginate(filters, order_by, page, page_size, ascending)` | `service.paginate` | Same. |
 | `count(filters)` | `service.count` | Same. |
-| `update(id, data)` | `service.update` | Same. |
+| `update(id, data)` | `service.update` | `data` typed by the optional 3rd generic param `UpdateT` (defaults to `BaseSchema`). |
 | `delete(id)` | `service.delete` | Same. |
 
 When a use case needs domain rules, override the inherited method in the service. When a use case needs to coordinate more than one service, override the inherited method (or add a new one) in the controller. The router never grows — it only depends on the controller.

{tempest_fastapi_sdk-0.78.0 → tempest_fastapi_sdk-0.79.0}/README.md

@@ -2023,7 +2023,7 @@ Each mixin owns its own env-var prefix — pick only the ones the service needs:
 
 `BaseService[RepositoryT, ResponseT]` and `BaseController[ServiceT, ResponseT]` are generic skeletons matching the SDK layering (router → controller → service → repository). They expose pass-through CRUD methods so simple endpoints can subclass them without overriding anything; you override only methods that need orchestration.
 
-What you inherit by subclassing `BaseService[RepositoryT, ResponseT]`:
+`BaseService[RepositoryT, ResponseT]` accepts an optional third type argument — `BaseService[RepositoryT, ResponseT, UpdateT]` — that types the `update` payload (defaults to `BaseSchema`, so the two-argument form keeps working). What you inherit by subclassing it:
 
 | Method | Returns | Notes |
 | --- | --- | --- |
@@ -2033,7 +2033,7 @@ What you inherit by subclassing `BaseService[RepositoryT, ResponseT]`:
 | `paginate(filters=None, order_by=None, page=1, page_size=20, ascending=True)` | `dict` with mapped `items` + `total`/`page`/`size`/`pages`. | Offset pagination via `repository.paginate`. |
 | `count(filters=None)` | `int` | Pass-through to `repository.count`. |
 | `exists(filters)` | `bool` | Pass-through to `repository.exists`. |
-| `update(id, data)` | `ResponseT` | Fetch by id, copy the fields present in `data` (a `BaseSchema`) onto the row, persist, map. `to_dict()` drops unset/`None`, so it serves PUT and PATCH alike. |
+| `update(id, data)` | `ResponseT` | Fetch by id, copy the fields present in `data` (typed `UpdateT`, the optional 3rd generic param — defaults to `BaseSchema`) onto the row, persist, map. `to_dict()` drops unset/`None`, so it serves PUT and PATCH alike. |
 | `delete(id)` | `None` | Hard delete via `repository.delete`. |
 
 `map_to_response` is `await`-ed when it returns a coroutine, so async mappers work transparently — no method override needed.
@@ -2046,7 +2046,7 @@ What you inherit by subclassing `BaseController[ServiceT, ResponseT]`:
 | `list(filters, order_by, ascending)` | `service.list` | Same. |
 | `paginate(filters, order_by, page, page_size, ascending)` | `service.paginate` | Same. |
 | `count(filters)` | `service.count` | Same. |
-| `update(id, data)` | `service.update` | Same. |
+| `update(id, data)` | `service.update` | `data` typed by the optional 3rd generic param `UpdateT` (defaults to `BaseSchema`). |
 | `delete(id)` | `service.delete` | Same. |
 
 When a use case needs domain rules, override the inherited method in the service. When a use case needs to coordinate more than one service, override the inherited method (or add a new one) in the controller. The router never grows — it only depends on the controller.

{tempest_fastapi_sdk-0.78.0 → tempest_fastapi_sdk-0.79.0}/docs/architecture.en.md

@@ -147,7 +147,7 @@ What you inherit by subclassing `BaseService[RepositoryT, ResponseT]`:
 | `paginate(filters=None, order_by=None, page=1, page_size=20, ascending=True)` | `dict` with mapped `items` + `total`/`page`/`page_size`/`pages`. | Offset pagination via `repository.paginate`. |
 | `count(filters=None)` | `int` | Pass-through to `repository.count`. |
 | `exists(filters)` | `bool` | Pass-through to `repository.exists`. |
-| `update(id, data)` | `ResponseT` | Fetch by id, copy the fields present in `data` (a `BaseSchema`) onto the row, persist, map. `to_dict()` drops unset/`None`, so it serves PUT and PATCH. |
+| `update(id, data)` | `ResponseT` | Fetch by id, copy the fields present in `data` (typed by `UpdateT`, the optional 3rd generic param — defaults to `BaseSchema`) onto the row, persist, map. `to_dict()` drops unset/`None`, so it serves PUT and PATCH. |
 | `delete(id)` | `None` | Hard delete via `repository.delete`. |
 
 `map_to_response` is `await`-ed when it returns a coroutine, so async mappers work transparently — no method override needed.

{tempest_fastapi_sdk-0.78.0 → tempest_fastapi_sdk-0.79.0}/docs/architecture.md

@@ -147,7 +147,7 @@ O que você herda ao subclassear `BaseService[RepositoryT, ResponseT]`:
 | `paginate(filters=None, order_by=None, page=1, page_size=20, ascending=True)` | `dict` com `items` mapeados + `total`/`page`/`page_size`/`pages`. | Paginação por offset via `repository.paginate`. |
 | `count(filters=None)` | `int` | Pass-through para `repository.count`. |
 | `exists(filters)` | `bool` | Pass-through para `repository.exists`. |
-| `update(id, data)` | `ResponseT` | Busca por id, copia os campos presentes em `data` (um `BaseSchema`) na instância, persiste e mapeia. `to_dict()` descarta unset/`None`, então serve PUT e PATCH. |
+| `update(id, data)` | `ResponseT` | Busca por id, copia os campos presentes em `data` (tipado por `UpdateT`, o 3º parâmetro genérico opcional — default `BaseSchema`) na instância, persiste e mapeia. `to_dict()` descarta unset/`None`, então serve PUT e PATCH. |
 | `delete(id)` | `None` | Hard delete via `repository.delete`. |
 
 `map_to_response` é aguardado com `await` quando retorna uma coroutine, então mappers async funcionam de forma transparente — sem precisar sobrescrever o método.

{tempest_fastapi_sdk-0.78.0 → tempest_fastapi_sdk-0.79.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "tempest-fastapi-sdk"
-version = "0.78.0"
+version = "0.79.0"
 description = "Shared FastAPI building blocks: base schemas, ORM model, async repository, exceptions, pagination and settings — the conventions used across Tempest projects."
 readme = "README.md"
 requires-python = ">=3.11"

{tempest_fastapi_sdk-0.78.0 → tempest_fastapi_sdk-0.79.0}/tempest_fastapi_sdk/__init__.py

@@ -342,7 +342,7 @@ from tempest_fastapi_sdk.websockets import (
     make_websocket_router,
 )
 
-__version__: str = "0.78.0"
+__version__: str = "0.79.0"
 
 __all__: list[str] = [
     "BASE_COLUMN_ORDER",

{tempest_fastapi_sdk-0.78.0 → tempest_fastapi_sdk-0.79.0}/tempest_fastapi_sdk/controllers/base.py

@@ -2,17 +2,23 @@
 
 from __future__ import annotations
 
-from typing import Any, Generic, TypeVar, cast
+from typing import Any, Generic, cast
 from uuid import UUID
 
+from typing_extensions import TypeVar
+
 from tempest_fastapi_sdk.schemas.base import BaseSchema
 from tempest_fastapi_sdk.services.base import BaseService
 
 ServiceT = TypeVar("ServiceT", bound=BaseService[Any, Any])
 ResponseT = TypeVar("ResponseT")
+UpdateT = TypeVar("UpdateT", bound=BaseSchema, default=BaseSchema)
+"""Update-payload schema for :meth:`BaseController.update`. Defaults to
+:class:`BaseSchema`, so ``BaseController[Service, Resp]`` still works;
+pass a third argument to type the payload precisely."""
 
 
-class BaseController(Generic[ServiceT, ResponseT]):
+class BaseController(Generic[ServiceT, ResponseT, UpdateT]):
     """Thin orchestration layer between routers and services.
 
     Following the SDK layering rules (router → controller → service →
@@ -25,6 +31,10 @@ class BaseController(Generic[ServiceT, ResponseT]):
     Generic parameters:
         ServiceT: The concrete service class.
         ResponseT: The response schema returned to the router.
+        UpdateT: The update-payload schema accepted by :meth:`update`.
+            Optional — defaults to :class:`BaseSchema`, so a two-argument
+            ``BaseController[Service, Resp]`` still works; supply it to
+            type the ``update`` payload precisely.
 
     Attributes:
         service (ServiceT): The service the controller delegates to.
@@ -113,12 +123,12 @@ class BaseController(Generic[ServiceT, ResponseT]):
         """
         return await self.service.count(filters)
 
-    async def update(self, id: UUID, data: BaseSchema) -> ResponseT:
+    async def update(self, id: UUID, data: UpdateT) -> ResponseT:
         """Pass-through to :meth:`BaseService.update`.
 
         Args:
             id (UUID): The primary key of the record to update.
-            data (BaseSchema): The update payload (unset fields skipped).
+            data (UpdateT): The update payload (unset fields skipped).
 
         Returns:
             ResponseT: The mapped, updated response.

{tempest_fastapi_sdk-0.78.0 → tempest_fastapi_sdk-0.79.0}/tempest_fastapi_sdk/services/base.py

@@ -3,17 +3,23 @@
 from __future__ import annotations
 
 import inspect
-from typing import Any, Generic, TypeVar
+from typing import Any, Generic
 from uuid import UUID
 
+from typing_extensions import TypeVar
+
 from tempest_fastapi_sdk.db.repository import BaseRepository
 from tempest_fastapi_sdk.schemas.base import BaseSchema
 
 RepositoryT = TypeVar("RepositoryT", bound=BaseRepository[Any])
 ResponseT = TypeVar("ResponseT")
+UpdateT = TypeVar("UpdateT", bound=BaseSchema, default=BaseSchema)
+"""Update-payload schema. Defaults to :class:`BaseSchema`, so a service
+declared as ``BaseService[Repo, Resp]`` keeps working; pass a third
+argument (``BaseService[Repo, Resp, MyUpdateSchema]``) to type ``update``."""
 
 
-class BaseService(Generic[RepositoryT, ResponseT]):
+class BaseService(Generic[RepositoryT, ResponseT, UpdateT]):
     """Thin business-logic layer wrapping a :class:`BaseRepository`.
 
     The default implementation exposes CRUD pass-through methods that
@@ -26,6 +32,11 @@ class BaseService(Generic[RepositoryT, ResponseT]):
     Generic parameters:
         RepositoryT: The concrete repository class.
         ResponseT: The response schema returned by the service.
+        UpdateT: The update-payload schema accepted by :meth:`update`.
+            Optional — defaults to :class:`BaseSchema`, so a two-argument
+            ``BaseService[Repo, Resp]`` still works; supply it
+            (``BaseService[Repo, Resp, MyUpdateSchema]``) to type the
+            ``update`` payload precisely.
 
     Attributes:
         repository (RepositoryT): The repository the service delegates to.
@@ -169,7 +180,7 @@ class BaseService(Generic[RepositoryT, ResponseT]):
         """
         return await self.repository.exists(filters)
 
-    async def update(self, id: UUID, data: BaseSchema) -> ResponseT:
+    async def update(self, id: UUID, data: UpdateT) -> ResponseT:
         """Apply a partial update to a record and map it to a response.
 
         Fetches the row by primary key, copies the fields present in
@@ -185,8 +196,8 @@ class BaseService(Generic[RepositoryT, ResponseT]):
 
         Args:
             id (UUID): The primary key of the record to update.
-            data (BaseSchema): The update payload. Fields left unset (or
-                ``None``) are not applied.
+            data (UpdateT): The update payload (a :class:`BaseSchema`).
+                Fields left unset (or ``None``) are not applied.
 
         Returns:
             ResponseT: The mapped, updated response.

{tempest_fastapi_sdk-0.78.0 → tempest_fastapi_sdk-0.79.0}/tests/controllers/test_base.py

@@ -46,11 +46,11 @@ class GadgetRepository(BaseRepository[Gadget]):
         )
 
 
-class GadgetService(BaseService[GadgetRepository, GadgetResponse]):
+class GadgetService(BaseService[GadgetRepository, GadgetResponse, GadgetUpdate]):
     pass
 
 
-class GadgetController(BaseController[GadgetService, GadgetResponse]):
+class GadgetController(BaseController[GadgetService, GadgetResponse, GadgetUpdate]):
     pass
 
 

{tempest_fastapi_sdk-0.78.0 → tempest_fastapi_sdk-0.79.0}/tests/services/test_base.py

@@ -50,7 +50,7 @@ class WidgetRepository(BaseRepository[Widget]):
         )
 
 
-class WidgetService(BaseService[WidgetRepository, WidgetResponse]):
+class WidgetService(BaseService[WidgetRepository, WidgetResponse, WidgetUpdate]):
     pass
 
 

{tempest_fastapi_sdk-0.78.0 → tempest_fastapi_sdk-0.79.0}/uv.lock

@@ -2822,7 +2822,7 @@ wheels = [
 
 [[package]]
 name = "tempest-fastapi-sdk"
-version = "0.78.0"
+version = "0.79.0"
 source = { editable = "." }
 dependencies = [
     { name = "alembic" },