docs: update specification — DomainBaseModel as shared Pydantic base for domain entities #2602

Merged
freemo merged 1 commits from spec/update-v3.7.0-domain-base-model into master 2026-04-05 21:19:00 +00:00

1 Commits

Author SHA1 Message Date
freemo 2f7e08a198 docs(spec): document DomainBaseModel as shared Pydantic base for domain entities
CI / lint (pull_request) Successful in 27s
CI / typecheck (pull_request) Successful in 49s
CI / security (pull_request) Successful in 58s
CI / quality (pull_request) Successful in 37s
CI / build (pull_request) Successful in 33s
CI / helm (pull_request) Successful in 22s
CI / unit_tests (pull_request) Successful in 9m57s
CI / docker (pull_request) Successful in 11s
CI / e2e_tests (pull_request) Successful in 18m38s
CI / coverage (pull_request) Successful in 11m2s
CI / integration_tests (pull_request) Successful in 22m35s
CI / status-check (pull_request) Successful in 1s
CI / benchmark-publish (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Successful in 57m27s
Update the Domain Models section of docs/specification.md to reflect the
introduction of DomainBaseModel (domain/models/base.py) as the shared Pydantic
base class for domain entities with the canonical model_config.

Changes:
- docs/specification.md: Update Domain Models subsection to mention
  DomainBaseModel and the canonical config (str_strip_whitespace,
  validate_assignment, arbitrary_types_allowed=False, populate_by_name,
  use_enum_values). Clarify that classes with different config requirements
  may still subclass BaseModel directly.

Triggered by PR #2014 (refactor(domain): extract shared model_config into
a base Pydantic model, closes #1941).
Approved via proposal issue #2440.

ISSUES CLOSED: #2440
2026-04-05 02:43:05 +00:00