docs(adr): add ADR 014 repository pattern over ORM#258
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds ADR 014 documenting the decision to use the Repository pattern instead of an ORM for database access. This captures the rationale behind the existing architecture — keeping the core layer database-agnostic with Valibot schemas as the single source of truth for entity shapes.
Changes
docs/adr/014-repository-pattern-over-orm.md— new ADR covering repository pattern, branded IDs, Valibot schema validation, and trade-offs vs ORMsdocs/adr/README.md— add ADR 014 to the index tableTesting