F15.4 — Domain errors in commons
| State | New |
| Parent | E15 |
| Tags | deferred |
| Predecessors | — |
| Source | E15 design |
| Entry criteria | the first non-web consumer of rn-forge-django or rn-forge-sqlalchemy, or E13 moving domain types out of rn-forge-web |
No stories yet.
Move VersionConflict and DomainConflict from rn-forge-web to commons as
domain errors, with web keeping the mapping to 409 problems. The ORM packages
then take no web import for their model layer. Making rn-forge-web an extra of
rn-forge-django is a possible follow-on.
Context
The design gives the facts.
Importing rn_forge.django.models loads rn_forge.web only through
rn_forge.django.models.concurrency. Today the cost is two small extra installs
and an import, so nothing is functionally broken. The move is breaking for
rn-forge-web, rn-forge-django and rn-forge-sqlalchemy, because
ADR-0002 forbids aliases. If E13's placement work
moves domain types out of web, these two belong in the same move.
Stories wait until the owner schedules the feature. Do not start or elaborate it before then.