Remove superseded Room MemberEntity/CanonicalNoteEntity scaffolding #46
Labels
No labels
bug
chore
feature
spike
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
utilities/Logbook#46
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Issue #17 scaffolded
MemberEntityandCanonicalNoteEntityinapp/src/main/java/family/marquezkeenan/logbook/data/db/Entities.kt(+ DAO/DB) as placeholders for family member config. Issue #20 delivered that config as a static, injectableFamilyMemberRegistryinstead (domain/FamilyMember.kt, domain/FamilyMemberRegistry.kt) — hardcoded, no Room involvement, no caching needed for compile-time constants. These entities are now dead scaffolding and a second source of truth risk; remove them (and any DAO/DB wiring referencing them) before the template/stream issues build further on the DB.This issue is stale — the scaffolding it targets no longer exists in the form described.
Entities.kt(bareMemberEntity/CanonicalNoteEntity) and the stubLogbookDao.ktfrom issue #17 were already deleted in issue #22's commit94d7c67("feat(00022): add Room entities, DAOs, and wire LogbookDatabase for the §9 data layer").Their present-day namesakes are different, live code, not dead scaffolding:
data/db/CanonicalNoteEntity.kt— offline cache of Outline doc bodies with arevisionconflict-detection baseline; referenced byCachedContentRepository,CacheRefreshEngine,EntrySyncEngine,LogbookDatabase,DatabaseModule, and covered by tests.data/db/MemberConfigEntity.kt— its docstring explicitly frames it as dynamic per-member state layered overFamilyMemberRegistry, which stays the compile-time source of truth for identity. This is the deliberate resolution of the exact "second source of truth" concern this issue raised, not a duplication of it.Both are part of the live schema (
LogbookDatabaseversion 4, migrations 1→4, exported schemas 1.json–4.json). Deleting them would break the caching/sync layer. Closing as superseded/no-longer-applicable.