Add single-collection inheritance for documents - #15
Merged
Conversation
DanielBadura
approved these changes
Aug 31, 2026
DavidBadura
force-pushed
the
inheritance
branch
from
August 31, 2026 13:27
b4e5065 to
53f9b46
Compare
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
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.
Document classes can now form a hierarchy that shares one collection. The root carries a #[DiscriminatorMap] attribute mapping a stable string to each concrete class; subclasses inherit the collection, database, id property and indexes. Every stored document gets a discriminator field (_type by default) so the hydrator can reconstruct the concrete class on load.
The repository for the root class is polymorphic: it accepts any subclass on write and returns concrete types on read. A repository for a concrete class is scoped to its own discriminator value, so its queries, counts and deletes never touch sibling types, and writes reject foreign types with WrongClass.
The metadata factory walks the parent chain to find the #[Document] class, validates the map and merges the field mappings of the whole hierarchy so you can filter by inherited and subclass-only properties from the root. Conflicting field names across subclasses raise DiscriminatorFieldConflict.